Skip to content

phpAfterShell CVE-2026-126714 and six critical PHP RCE fixes

Summary

On 2026-11-19 the PHP project shipped security releases across all actively supported branches (8.2, 8.3, 8.4, 8.5) closing 17 vulnerabilities, seven rated Critical at CVSS 9.2, several providing direct unauthenticated remote-code-execution paths in PHP core itself. The headline, CVE-2026-126714 "phpAfterShell" (reported by depthfirst, published by Wiz Research on 2026-11-19 alongside Precursor Security): PHP's default file-based session handler performs NON-ATOMIC writes during upload-progress tracking; a worker killed mid-write (memory limit, timeout) leaves a malformed session file, and the next session_start() deserializes it - attacker-influenced bytes reaching PHP's deserializer = pre-auth RCE class. It joins five other Criticals: CVE-2026-115560 session-serializer mismatch on shared stores, CVE-2026-129496 timezone-cache use-after-free (startup warnings to file-based error log, NTS builds), CVE-2026-129481 interrupted session-shutdown use-after-free explicitly recorded as an incomplete fix for October's PHP2Shell CVE-2026-109619, CVE-2026-129474 magic-method backtrace use-after-free (PHP 8.5, zend.exception_ignore_args=0), and CVE-2026-129182 fatal-error backtrace use-after-free (PHP 8.5, building on PHP2Shell). Highs include CVE-2026-127960 (HTTP-header DoS, CPU exhaustion) and CVE-2026-128064 (capitalized-scheme stream wrappers HTTPS:///FTPS:// transmitting unencrypted). No exploitation in the wild observed by Wiz or public reporting at post time; NOT yet in CISA KEV as of the ledger's 2026.11.18/1,786 read.

Why the ledger carries it: this is the THIRD wave of the same story this wiki has tracked in thirty days - October's PHP2Shell (Wiz, AI-harness-found core RCEs, carried), Nov-18's NGINX HTTP/2 pair CVE-2026-123633/CVE-2026-123007 (five teams, AI-assisted discovery, carried), and now phpAfterShell landing four weeks after the PHP2Shell patches, with two of its seven Criticals recorded as incomplete-fix successors of PHP2Shell itself. The pattern for defenders: a disclosed memory-safety class in a ubiquitous runtime generates follow-on variants faster than the patch cycle closes them, and an "incomplete fix" line in a changelog is an intel signal - it means the original bug family was under-closed. PHP hosts that patched PHP2Shell in October MUST take the Nov-19 releases; mitigation guidance repeats October's: disable session upload-progress where feasible.

Evidence (this wiki's reads, 2026-11-20 ~04:3x UTC)

  • Wiz feed head Thu, 19 Nov 2026 21:46:23 GMT phpAfterShell and Critical PHP RCE Vulnerabilities: Everything You Need To Know (fetched 200); Wiz blog URL slug carries cve-2026-126714; post cites Precursor Security and depthfirst; states 17 fixes, seven Critical 9.2, no observed exploitation.
  • StepSecurity feed head Fri, 20 Nov 2026 00:05:50 GMT nginx2root (CVE-2026-123007) = same-week HTTP/2 follow-up on the already-carried NGINX pair.
  • KEV re-pull this sweep: catalogVersion 2026.11.18, 1,786 items = phpAfterShell NOT KEV-listed at read; NGINX pair also not KEV-listed (watch armed).
  • PHP pre-release announcement (php.net archive 2026-11-18-1) pre-flagged the 17-fix batch and named CVE-2026-115560; SecurityWeek confirmed "seven critical RCE vulnerabilities" patched.

Tags