The PHP project released security updates on November 19 that fix eight vulnerabilities, seven of them rated critical (CVSS 9.2). Several could allow remote code execution, but the project said the critical issues need non-default or uncommon setups. Fixed versions are PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0.
What happened
On November 18 the maintainers warned that a release scheduled for November 19 would address vulnerabilities in all supported PHP versions, with a top severity of critical. The fixes shipped on schedule. The official changelog lists the advisories below; the conditions come from reporting by The Hacker News.
| CVE | CVSS | Flaw | Reported conditions |
|---|---|---|---|
CVE-2026-115560 | 9.2 | Session serializer mismatch; RCE | Code switches session.serialize_handler to php via ini_set() before session_start(); upload progress enabled (the default) |
CVE-2026-126714 | 9.2 | Partially overwritten session files ("phpAfterShell") | Attacker influences session data, an interrupted write, and a suitable deserialization gadget chain |
CVE-2026-129289 | 9.2 | PHP-FPM request smuggling | Persistent backend connections plus an app path that opens php://input without fully reading it |
CVE-2026-129474 | 9.2 | Use-after-free in magic method backtraces | PHP 8.5 and later; request-data control, a reachable magic method, a fatal error |
CVE-2026-129182 | 9.2 | Use-after-free after a fatal error | Fixed in 8.5.13 and 8.6.0 |
CVE-2026-129481 | 9.2 | Use-after-free after interrupted session shutdown | Can corrupt memory or crash a reused worker |
CVE-2026-129496 | 9.2 | Timezone cache use-after-free | Unauthenticated remote attacker could crash workers or run code |
CVE-2026-129291 | 8.8 | PHP-FPM epoll use-after-free; local privilege escalation | Needs local code execution in an FPM worker |
Security firm Depthfirst, which named CVE-2026-126714 "phpAfterShell", described how an interrupted session write can leave a spliced session file that PHP later deserializes. The changelog also lists other security fixes in PHP-CGI, DOM, SOAP and Phar.
Who is affected
Any server running a supported PHP branch before the fixed releases is in scope, including sites on shared hosting, WordPress, Drupal and custom PHP-FPM stacks. Real exposure depends on configuration: the sources describe specific session, FastCGI and application conditions for the most serious bugs. The fixed list covers only 8.2 through 8.6; the project said in its October advisory that PHP 8.1 and older no longer receive project updates.
This is separate from the October PHP2Shell flaws (CVE-2026-109618 and CVE-2026-109619), which The Hacker News reports came under limited exploitation. The sources we reviewed do not report exploitation of the November flaws.
What to do
Steps 1 to 3 are our analysis; the interim mitigation in step 4 is from The Hacker News.
- Check your version with
php -vand upgrade to 8.2.36, 8.3.37, 8.4.28 or 8.5.13 (or 8.6.0). - Restart PHP-FPM or web server workers so the new binary is loaded, and rebuild any container images based on older PHP.
- On managed hosting, ask your provider which PHP build your site runs. Move off PHP 8.1 or older.
- If you cannot patch right away, set
session.upload_progress.enabled=0and restart workers; this addressesCVE-2026-115560only.
What we still do not know
The PHP project has not said whether any of these flaws are being exploited, and we did not find confirmed exploitation. We also do not know how many servers meet the conditions for the most serious bugs, or how quickly Linux distributions will ship backported fixes.
Sources: The Hacker News, PHP Fixes 7 Critical Flaws (Nov. 19, 2026); The Hacker News, PHP Warns of Critical Security Flaws (Nov. 19, 2026); PHP 8 ChangeLog, php.net (Nov. 19, 2026); PHP news archive, php.net (Oct. 21, 2026 advisory).
Leave a Reply