CVEHit Business Advisory by IntegrityLab.ai
What should we do?
PHP session and PHP-FPM flaws (phpAfterShell) — CVE-2026-126714, CVE-2026-129289, CVE-2026-115560: Business Triage
Do Now
- System owner: update PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 on its current branch, then restart PHP-FPM or the web server.
Proof the update is done
- A reload may leave old PHP workers running. Restart so every worker runs the new build.
- Completion evidence for each server:
- PHP version serving web requests after the update.
- Source of that record.
- Date checked.
- Operations owner: where the update must wait, turn off session upload progress and backend connection reuse until it is done.
What to change
- Set session.upload_progress.enabled = 0 in php.ini or the FPM pool, then restart every worker. depthfirst says this removes the easiest path to phpAfterShell, not the flaw itself, and PHP says it does not protect applications that put attacker-controlled data into sessions in other ways. It also removes the attack path for CVE-2026-115560.
- Turn off nginx fastcgi_keep_conn or Apache enablereuse for PHP-FPM backends. PHP lists this as the interim step for CVE-2026-129289.
- Confirm the application still works after each change.
- Provider: ask each hosting or software vendor that runs PHP for you which PHP build it uses and when the fix ships.
What to ask
- Ask for:
- The PHP version or package serving your sites.
- Whether it includes the November 19, 2026 fixes.
- The fix date.
Do Next
- Security owner: recheck CISA, the KEV catalog and the PHP advisories for changes to the exploitation status.
What to recheck
- depthfirst says parts of its code execution chain, including the decoder and final heap layout, remain reserved for coordinated disclosure. Watch depthfirst and PHP for full details.
- PHP 8.2 security support ends December 31, 2026. Plan a move to a newer branch.
← Back to article questions