CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to the live brief
NOTABLECVE-2026-129289 +7NATOA2vulnerability

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36: CVE-2026-129289 lets an unauthenticated request smuggle a second FastCGI request into PHP-FPM and run PHP code when the front end reuses FastCGI connections; the release also fixes the session flaw left open in October and follow-ups to an incomplete earlier fix (CVSS 4.0 9.2)

PHP 8.5.13, 8.4.28, 8.3.37, 8.2.36: FPM request smuggling to code execution; the open session flaw is fixed

Defender actions

  • On every PHP-FPM server behind nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on or HAProxy in FastCGI mode, switch FastCGI backend connection reuse off until the server runs 8.2.36, 8.3.37, 8.4.28 or 8.5.13, because CVE-2026-129289 gives an unauthenticated request code execution as the worker wherever a connection is reused and an application path leaves php://input unread.

Analysis

The PHP project released 8.5.13, 8.4.28, 8.3.37, 8.2.36 and 8.6.0 on 2026-11-19, and the changelogs list up to 18 CVEs per branch (PHP, 2026-11-19). The most direct is CVE-2026-129289: when php://input was opened but not read to the end, PHP-FPM leaves the unread request bytes on a persistent FastCGI connection, so a malformed multipart body can place a second FastCGI request inside the first, and an unauthenticated attacker can bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker (PHP, 2026-11-19). It requires a front end that enables persistent backend connections and an application path that opens php://input without reading it fully; standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated attack (PHP, 2026-11-19).

Two session flaws close the item the October release left open (watchTowr, 2026-11-20): CVE-2026-115560, where upload-progress session data is written in one serializer format and read in another, and CVE-2026-126714, where an interrupted write by the default files handler leaves a mixed old and new session file; both end in object injection and need an object gadget chain in the application (PHP, 2026-11-19; PHP, 2026-11-19). The fix for the first disables upload progress by default (PHP, 2026-11-19). CVE-2026-129481, a use-after-free of a stale session filename after an interrupted session shutdown, is in PHP's words an incomplete fix for CVE-2026-109619 and affects PHP 8.3 and later, and CVE-2026-129182, for PHP 8.5 only, covers further scenarios after the 8.5.12 fix (PHP, 2026-11-19; PHP, 2026-11-19).

CVE-2026-129474, PHP 8.5 only, is exposed on the built-in defaults, because fatal error backtraces are on in 8.5 and the default includes arguments, and php.ini-production, which sets zend.exception_ignore_args=1, or fatal_error_backtraces=0 prevents the attack; PHP confirmed code execution on 8.5 (PHP, 2026-11-19). CVE-2026-129496 needs a startup diagnostic written through a file-based error_log in a non-thread-safe build (PHP, 2026-11-19). CVE-2026-129291, an epoll use-after-free in PHP-FPM, gives root from a worker where catch_workers_output is on and the FPM master runs as root (PHP, 2026-11-19). NCSC.ch lists exploitation as unknown with no public proof of concept referenced, and watchTowr reports none as of 2026-11-20 (NCSC.ch, 2026-11-19; watchTowr, 2026-11-20).

Sources11

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.