> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/release-notes/inforiver-writeback-matrix/inforiver-writeback-matrix-october-2026-v4.6.17.0.md).

# Inforiver Writeback Matrix October 2026 - v4.6.17.0

This update delivers critical security vulnerability patches across runtime and browser components, along with key bug fixes to improve report navigation and row management.

### Security updates – vulnerability fixes&#x20;

This release addresses several security vulnerabilities across runtime and browser components. The following vulnerabilities have been addressed as part of this patch:&#x20;

* Google Chrome: [CVE-2026-87492](https://nvd.nist.gov/vuln/detail/CVE-2026-87492), along with several other high- and medium-severity vulnerabilities related to Google Chrome.&#x20;
* Node.js Runtime – Broccoli2Shell: [CVE-2026-111497](https://nvd.nist.gov/vuln/detail/CVE-2026-111497).&#x20;
* Additional Security Fixes: Several other medium- and low-severity vulnerabilities have also been addressed.&#x20;

PHP2Shell – Not Applicable to Inforiver&#x20;

The PHP2Shell vulnerabilities ([CVE-2026-109618](https://nvd.nist.gov/vuln/detail/CVE-2026-109618) and [CVE-2026-109619](https://nvd.nist.gov/vuln/detail/CVE-2026-109619)) do not affect Inforiver, as the product does not use PHP.&#x20;

### Issues fixed:&#x20;

1. Resolved an issue where row grouping was reset or lost when navigating across report pages.&#x20;
2. Addressed an issue preventing the **Insert Rows** option from functioning as expected in custom reports.&#x20;

We recommend keeping your deployment updated with the latest available patch to benefit from the security fixes included in this release.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.inforiver.com/release-notes/inforiver-writeback-matrix/inforiver-writeback-matrix-october-2026-v4.6.17.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
