As reported by The Hacker News, a critical vulnerability in PHP's default file-based session storage mechanism — dubbed phpAfterShell (CVE-2026-126714, CVSS 4.0: 9.2) — enables remote code execution through a race-condition-style session write cutoff combined with an application-level deserialization gadget chain. Today's PHP releases across all active branches ship the fix.
Vulnerability Overview
| Field | Detail |
|---|---|
| CVE | CVE-2026-126714 |
| CVSS 4.0 | 9.2 (Critical) |
| Affected Component | PHP files session handler (default session storage) |
| Affected Branches | PHP 8.2 (<8.2.36), 8.3 (<8.3.37), 8.4 (<8.4.28), 8.5 (<8.5.13) |
| Fixed Releases | 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
| Active Exploitation | None reported at time of disclosure |
| Discoverer | Depthfirst |
| October PHP2Shell Fixes | Do NOT contain this patch — servers updated Oct 21 remain vulnerable |
Why This Matters
PHP powers roughly 75% of the web, and the majority of deployments use the default file-based session handler — the exact component at fault here. The attack surface is enormous. What makes phpAfterShell particularly insidious is that it doesn't require a traditional authentication bypass or input validation failure in the application itself. Instead, it exploits a timing window in how PHP serializes and writes session data to disk, allowing an attacker to influence which objects get deserialized on the next request.
The session.upload_progress feature is the most accessible attack vector: any PHP application that opens a session on a page reachable by an unauthenticated user can be exploited if the feature is enabled — and it is enabled by default. The attacker doesn't need a file upload form in the application; they simply craft a multipart request that triggers PHP's built-in upload progress tracking, which writes to the session before application code executes.
The critical insight: this is a deserialization-of-untrusted-data problem at the language runtime level, not the application level. Even well-coded apps with no known gadget chains are exposed if any installed library or framework ships one.
Who Is Most at Risk
session.upload_progress.enabled = 1 (the PHP default) and any unauthenticated session-opening endpointShield53 Recommendations
Immediate Actions
- Patch now: Upgrade to PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, or 8.6.0. Verify the running version with
php -vand confirm the web SAPI (not just CLI) is updated — checkphpinfo()orphp-fpmservice status - If you patched on October 21 for PHP2Shell: You are still vulnerable. Patch again with today's releases
- Interim mitigation (if patching is delayed): Set
session.upload_progress.enabled = 0inphp.iniand restart PHP-FPM workers. This closes the most accessible attack path but is NOT a complete fix - Audit session data: Review what untrusted data your application stores in
$_SESSION. Any attacker-controllable values create potential deserialization vectors independent of upload progress - Rebuild containers: Rebuild all PHP-based container images from updated base images and redeploy. Don't rely on runtime patching of running containers
- Consider Redis/DB session storage: Migrating away from the file handler eliminates this entire class of vulnerability. This is the strongest architectural mitigation, though each alternative store should be independently reviewed for truncation behavior
- Retire PHP 8.1 and older: These branches are end-of-life. The EOL mitigation backports for 7.4/8.0/8.1 are not affected, but any unpatched builds are. Migrate to a supported branch immediately
Detection Guidance
- Monitor for rapid, repeated multipart POST requests containing
session.upload_progress_prefixed field names — this pattern indicates potential exploitation attempts via the upload progress vector - Deploy WAF rules to flag multipart requests with upload progress metadata hitting endpoints that don't expect file uploads
- Watch for unexpected PHP-FPM worker restarts or child process spawning following session-heavy traffic
- Log and alert on
unserialize()or session deserialization errors in application logs
The broader takeaway: language-level session handling has been a persistent source of deserialization vulnerabilities across PHP, Java, and .NET ecosystems. Organizations should treat session storage configuration as a first-class security control, not a deployment default. The combination of file-based sessions, enabled upload progress, and any gadget chain in the dependency tree creates a reliable RCE primitive that no application-level hardening can fully neutralize. Patch today.