Short answer
CVE-2026-129481 is a use-after-free in PHP's session extension, rated 9.2 (critical) by the PHP project. It affects PHP 8.3 before 8.3.37, 8.4 before 8.4.28 and 8.5 before 8.5.13. It is hard to trigger and no attacks are known, but the same release of 19 November 2026 fixes 16 more flaws, including several that can lead to remote code execution on common setups. Upgrade every PHP server to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 this week.
- 9.2 - CVSS v4 score the PHP project gives CVE-2026-129481
- 17 - security flaws fixed in the 19 November 2026 releases
- 7 - of them rated critical (9.0 or higher)
- 4 - supported PHP branches patched: 8.2, 8.3, 8.4 and 8.5
On 19 November 2026 the PHP project released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Our newsroom flagged CVE-2026-129481 first: a critical-rated memory flaw in the session extension, which almost every PHP application uses for logins and shopping carts. Looking closer, it is one of 17 security fixes in the same release, and several of the others matter more for typical servers.
This guide explains CVE-2026-129481 in plain English, why its 9.2 score overstates the everyday risk, which of the other 16 flaws deserve attention first, how to check your servers and what to change in your configuration while you upgrade. It is written for CTOs, engineering managers and the developers who look after PHP in production.
What CVE-2026-129481 is, in plain English
When a PHP script starts a session, the session extension remembers the name of the file being run. At the end of the request PHP tears the session down and frees the memory the request used. If a fatal error happens in your own code during that teardown, for example in the stream\_close() method of a custom stream wrapper, the session extension keeps a pointer to the file name after the memory behind it has been freed.
PHP workers are reused. The next request handled by the same PHP-FPM or Apache worker can then free that stale string a second time. This kind of bug, called a use-after-free, can crash the worker or corrupt its memory. The PHP project notes that code execution has not been demonstrated.
One more condition limits it: the file name has to live in request memory, which happens when the script is not cached by OPcache. Most production servers run OPcache, so for them the file name sits in shared cache memory and the bug is much harder to reach.
Why a 9.2 score does not mean drop everything for this one
CVSS scores describe the worst plausible outcome, not the likely one. The vector for CVE-2026-129481 shows a network attacker with no login and full impact on confidentiality, integrity and availability, which is why it scores 9.2. The same vector also marks the attack complexity as high and says special conditions must be present.
CISA's own assessment, published with the NVD record, agrees: no known exploitation, not automatable, though total technical impact if someone succeeds. In business terms, this is a flaw to fix in your next scheduled patch window rather than an emergency, provided OPcache is on. The release as a whole is a different matter, as the next sections show.
QuestionCVE-2026-129481Affected versions8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13 (8.2 is not affected)ComponentSession extension (ext/session)Login neededNoPreconditionsA fatal error in application code during session shutdown, and the script not cached by OPcacheWorst outcomeWorker crash or memory corruption; code execution not demonstratedKnown exploitationNone reported as of 19 November 2026FixUpgrade to 8.3.37, 8.4.28 or 8.5.13
The rest of the 19 November release: what matters most
The same releases fix 16 more vulnerabilities. We have grouped them by what an attacker can do and what has to be true of your setup, because that is what decides your priorities.
Critical: remote code execution under realistic conditions
CVEScoreWhat it isExposed ifCVE-2026-1292899.2PHP-FPM request smuggling: leftover request body bytes are read as a new FastCGI request with attacker-chosen settingsThe web server reuses FastCGI connections (nginx fastcgi_keep_conn on, Apache enablereuse=on)CVE-2026-1267149.2Interrupted writes to session files can mix old and new data, letting attackers inject objectsDefault file session storage, with session upload progress or other attacker-influenced session dataCVE-2026-1155609.2Session serializer mismatch lets upload-progress data be unserialized as objectsUpload progress is on and session.serialize_handler differs at runtime or between apps sharing a session storeCVE-2026-1294969.2Timezone cache use-after-free from early diagnostics; code execution demonstrated with known addressesNon-thread-safe builds logging startup warnings to a file-based error_logCVE-2026-1294749.2Use-after-free in backtraces of __call() and __callStatic()PHP 8.5 with zend.exception_ignore_args disabled (php.ini-production enables it)CVE-2026-1291829.2Use-after-free of the stored fatal error backtrace after shutdownPHP 8.5 with specific per-directory or per-pool settings
Two of these deserve special attention. CVE-2026-129289 needs no login and can let an attacker run PHP code of their choosing, but only where the front-end server keeps FastCGI connections open between requests. That is not the default, yet it is a common performance tweak. CVE-2026-126714 and CVE-2026-115560 both turn session data into an object-injection route, and object injection is how many past PHP compromises worked once an application or framework offered a usable gadget chain.
High: data exposure, privilege escalation and code tampering
CVEScoreWhat it isCVE-2026-1292918.8PHP-FPM master use-after-free lets local PHP code gain the master's privileges, often root. Requires catch_workers_output, which the official PHP-FPM Docker images enable.CVE-2026-1279608.7Folded HTTP response headers keep workers busy parsing, a denial of service when PHP fetches attacker-controlled URLs.CVE-2026-1280648.2URLs written as HTTPS:// or FTPS:// in capitals, or received as redirects, are fetched without TLS, exposing credentials and data on the network.CVE-2026-1280907.7An attacker who can modify an OpenSSL-signed Phar archive can downgrade its signature type and get altered code accepted.
Shared hosting and multi-tenant platforms should treat CVE-2026-129291 as urgent: anyone who can upload PHP code to one site could take over the PHP-FPM master that serves every site. Container users should check their images, since the official Docker images turn on the setting it needs.
Moderate: crashes, leaks and edge cases
- CVE-2026-129538 (6.9): out-of-bounds memory access in php-cgi during PATH_INFO correction. PHP-FPM and mod_php are not affected.
- CVE-2026-129292 (5.3): cross-site scripting in the PHP-FPM full status page, which can also break monitoring tools reading its JSON or XML.
- CVE-2026-129501 and CVE-2026-129506 (6.3): crashes in the new DOM serializer and the SOAP extension when handling crafted XML.
- CVE-2026-15353 (6.3): four bytes of heap memory can leak through SOAP array decoding.
- CVE-2026-129438 (6.3): the PHP 8.5 RFC 3986 URI class can return a truncated string for inputs near 2 GiB.
Who is affected
BranchFixed versionSupport statusPHP 8.58.5.13Active supportPHP 8.48.4.28Active supportPHP 8.38.3.37Security fixes onlyPHP 8.28.2.36Security fixes only, ending 31 December 2026PHP 8.1 and olderNo fixEnd of life: these flaws will not be patched
Every supported branch needs this update. CVE-2026-129481 itself skips 8.2, but most of the other flaws do not. If you still run 8.1 or older, these fixes will never reach you from php.net; your options are a commercial long-term support build, a Linux distribution that backports fixes, or an upgrade. Our PHP 8.2 end-of-life guide covers planning that move.
Remember the PHP inside things you do not think of as PHP servers: WordPress, Drupal and Magento hosting, Laravel and Symfony applications, Docker images, CI runners, and appliances or control panels that bundle their own PHP.
How to check your servers
Run these on each server or inside each container image. Check the PHP that serves web traffic, not only the command-line PHP, because they can differ.
# 1. Which PHP version is running? php -v # 2. Is OPcache enabled for the web SAPI? (check phpinfo() from FPM too) php -i | grep -E "^opcache.enable" # 3. Settings that widen exposure to other flaws in this release php -i | grep -E "session.upload_progress.enabled|session.serialize_handler|session.save_handler|zend.exception_ignore_args" # 4. PHP-FPM pools: catch_workers_output and the status page grep -RnE "catch_workers_output|pm.status_path" /etc/php*/ /usr/local/etc/php-fpm.d/ 2>/dev/null # 5. Front end: are FastCGI connections reused? grep -RnE "fastcgi_keep_conn|enablereuse" /etc/nginx /etc/apache2 /etc/httpd 2>/dev/null Distribution packages often keep an older version number while including fixes. If php -v reports a version below the fixed ones, check your vendor's security tracker for these CVE numbers before you conclude you are exposed.
What to do now
- Upgrade. Move to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or your distribution's patched packages, then restart PHP-FPM or Apache so workers load the new binary. Rebuild container images rather than patching running containers.
- Start with the most exposed servers. Internet-facing applications, shared hosting, anything that reuses FastCGI connections and any server where users can upload PHP code.
- Keep OPcache on in production. It removes a precondition for CVE-2026-129481 and is a performance win anyway.
- Apply the configuration hardening below where you cannot upgrade immediately. It reduces exposure to the most serious flaws but does not replace the upgrade.
- Plan your end-of-life branches. Put a date on every application still on PHP 8.2 or older.
Configuration hardening while you upgrade
SettingChangeReduces exposure tosession.upload_progress.enabledSet to Off unless you use upload progress barsCVE-2026-126714, CVE-2026-115560session.serialize_handlerUse one value everywhere, never change it at runtimeCVE-2026-115560nginx fastcgi_keep_conn / Apache enablereuseTurn off connection reuse to PHP-FPMCVE-2026-129289zend.exception_ignore_argsSet to On, as php.ini-production doesCVE-2026-129474catch_workers_outputSet to no in FPM pools where you do not need itCVE-2026-129291pm.status_pathDisable, or restrict to internal addressesCVE-2026-129292opcache.enableKeep On for web SAPIsCVE-2026-129481
; php.ini – temporary hardening until every server runs the fixed versions session.upload_progress.enabled = Off zend.exception_ignore_args = On opcache.enable = 1 Test before you switch things off
Turning off upload progress removes progress bars for large uploads, and disabling FastCGI connection reuse adds a little latency per request. Both are usually acceptable for a few days, but check with the teams who own each application.
A one-week patch plan for engineering leaders
A release with 17 fixes across four branches is easy to underestimate. The upgrade itself is usually quick; finding every PHP runtime and coordinating restarts is what takes time. This plan fits a typical organisation with a handful of applications and a mix of virtual machines and containers.
DayActionOwnerDay 1Build the inventory: every server, container image, CI runner and vendor product that runs PHP, with its version and SAPI (FPM, mod_php, CGI)Platform or operations leadDay 1Check the exposure settings from this guide on each runtime and flag high-priority hostsPlatform or operations leadDay 2Apply the temporary hardening on high-priority hosts that cannot be upgraded the same dayOperationsDays 2–3Upgrade staging environments and rebuild container images on the fixed versions; run automated testsApplication teamsDays 3–5Roll out to production, internet-facing and shared hosts first, with a rollback planOperations with application teamsDays 5–7Confirm versions everywhere, remove hardening that hurts users, record exceptions with an owner and a dateEngineering manager
Questions to ask vendors. For hosted platforms and appliances you do not patch yourself, ask three things in writing: which PHP versions they run, whether the 19 November fixes are applied, and if not, when. Keep the answers with your risk register.
How to know you are done. Every PHP runtime in the inventory reports a fixed version or a vendor-confirmed backport, no host relies on hardening alone, and every application on an end-of-life branch has a dated upgrade plan.
What this release says about PHP security in 2026
This is the second large PHP security release in two months, after the October 2026 release. Several of the fixes are use-after-free bugs in shutdown and error paths, code that rarely runs in normal testing but that attackers can force. The PHP project now publishes detailed advisories with CVSS v4 scores for each one, which makes it easier to judge real exposure instead of reacting to headlines.
For leaders, the lesson is about process more than any single CVE. Teams that can rebuild and redeploy every PHP service within a week, from an up-to-date inventory, treat a release like this as routine maintenance. Teams that cannot, because of unknown PHP versions, hand-built servers or applications stuck on old branches, carry growing risk with every release. That gap is worth closing before the next one.
Sources
- PHP security advisory GHSA-g3vh-838c-65v7 for CVE-2026-129481 (GitHub)
- NVD entry for CVE-2026-129481, including CISA's assessment
- PHP 8 ChangeLog: 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (php.net)
- Supported PHP versions (php.net)
Are we covered?
- Do we know every place PHP runs, including containers, CI and vendor appliances, and which version each uses?
- When will every server run 8.5.13, 8.4.28, 8.3.37, 8.2.36 or a patched distribution package?
- Do any of our web servers reuse FastCGI connections to PHP-FPM?
- Is session upload progress switched on anywhere we do not need it?
- Which applications are still on PHP 8.2 or older, and what is the upgrade date for each?
Application security
Need help patching PHP across your estate?
We can inventory your PHP versions, roll out the November updates safely, apply the hardening settings and plan upgrades for end-of-life branches.
Originally published at phpscientist.com.
![Physical AI Engineering — Ch.13: Computing Platforms for Physical AI [EN]](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fg3ou3b2eumf1epqj4bk4.png)

![Physical AI Engineering — Ch.04: Localization Mapping and World Understanding [EN]](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuscy0mautxl2mb4834vd.png)