The 28 October batch adds two CISA KEV entries, both due 10 November: an upload flaw in Magento and Commerce, and a decoder bug in Brotli that ships inside Node.js 1. Separately, CISA listed the PHP pair on 26 October with a date of 29 October, and that lands first 1. PHP gets the work first; the other two are inventory questions on a longer clock.

PHP is due on 29 October

CVE-2026-109618 and CVE-2026-109619 are remote code execution in PHP core, 9.2 each under the PHP team’s CVSS v4.0 scoring 2. CISA added both on 26 October, five days after the fixed builds went out, and the federal date is 29 October 1.

The two bugs reach memory by different routes, and the 22 October writeup covers both: php2shell, the leaked PHP core RCE.

Anything serving PHP 8.2 through 8.5 that has not moved to 8.2.35, 8.3.36, 8.4.27 or 8.5.12 still carries the bug 234. The branches below 8.2 get no upstream fix, and 8.2 itself leaves security support on 31 December 2026 2.

The check that matters is which interpreter answers requests. My own box reports PHP 8.5.12 on the CLI, built on 21 October, and that tells me nothing about a pool serving traffic under a different build or a distribution package carrying its own revision. Backports land as package revisions, so reading the version off the wrong binary is how I would mark a host done while its traffic still hits the bug.

At work I turn that question into a list: which hosts, which branch, who owns each. The ordering and the reasoning behind it are my part, and the deployment side is automated once the owner has the build.

Magento and Commerce: a July patch, an October listing

CVE-2026-48356 is 9.3 under CVSS v3.1, an unrestricted upload of a file with a dangerous type (CWE-434) 5. The vector needs no credentials and does need a user to interact with the page, so the path runs through someone who holds a session rather than straight at the application.

Adobe published APSB26-73 on 14 July 2026 as a priority 2 bulletin covering fourteen records in Commerce and Magento Open Source, and said at publication that it knew of no exploitation in the wild 6. The bulletin covers the 2.4.9, 2.4.8-p5 and 2.4.7-p10 lines 6. CISA added the CVE on 27 October with a 10 November date 1.

The gap between the fix and the listing is fifteen weeks. A storefront that took the July build is not on this list, and the entry names the ones that did not. That is a different question with a different owner, because the team running the storefront is usually not the team running the patch cycle.

Before 10 November I want three things from the instance list: how many of each line, a named owner for each one, and whether the admin path answers from the internet. An upload endpoint behind an authenticated session is where mail filtering and network rules stop being useful, so the answer has to come from that list.

Brotli: a decoder bundled into other software

CVE-2026-111497 is 9.2 under CVSS v4.0, an out-of-bounds write in the Brotli decoder 7. The mechanism and the fixed releases are in the deep dive: Brotli, the 9.2 out-of-bounds write.

CISA added it on 27 October with the same 10 November date as Magento 1.

Exposure here depends on what you inherited, because the library comes with a runtime, with a distribution package, or with a proxy that vendored it. The version that matters sits in a package manifest, not in a service banner. On this machine the package is brotli 1.2.1, the shared object is libbrotlidec 1.2.1, and Node v24.22.1 reports a bundled Brotli of 1.2.1, so all three sit outside the affected range. Those checks took two minutes and answered by version number.

I have no observation of exploitation against anything I run. I treat the KEV entry as a schedule and a prompt to look, and I keep it separate from what I can see on my own estate.

The fixes came before the listing

Both deadlines land on records whose fixed builds predate the KEV entry: 21 October for PHP, July for Commerce, 21 October for Node. Nobody has to write new code for any of them. The work left is inventory, finding the hosts that never took a build and learning who owns each one, and that takes longer than the patching does.


  1. Cybersecurity and Infrastructure Security Agency. (2026, October 27). Known exploited vulnerabilities catalog (catalogVersion 2026.10.27). CISA. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  2. Webb, M. (2026, October 21). PHP core RCE CVE-2026-109618 and CVE-2026-109619: patch and exposure. Phoenix Security. https://phoenix.security/php-core-rce-cve-2026-109618-109619-critical-remote-code-execution/ ↩︎ ↩︎ ↩︎

  3. National Vulnerability Database. (2026, October 21). CVE-2026-109618 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-109618 ↩︎

  4. National Vulnerability Database. (2026, October 21). CVE-2026-109619 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-109619 ↩︎

  5. National Vulnerability Database. (2026, July 14). CVE-2026-48356 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-48356 ↩︎

  6. Adobe. (2026, July 14). Security update available for Adobe Commerce (APSB26-73). Adobe. https://helpx.adobe.com/security/products/magento/apsb26-73.html ↩︎ ↩︎

  7. National Vulnerability Database. (2026, October 22). CVE-2026-111497 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-111497 ↩︎