Vulnerability · on the rundown Wednesday, October 21, 2026
PHP releases emergency fixes for two PHP2Shell code execution flaws
Covered by 18 outlets over 11 hours. First reported by CyberSecurityNews at 03:34 UTC on October 21, 2026.
- outlets18
- distinct reports18
- first to latest report11 h
- names in it9
What happened?
- The PHP security team said the risk is highest for mod_php, citing a demonstrated exploit in which an unauthenticated request triggers the attack before any application code runs.
- CVE-2026-109619 is a stale global state vulnerability enabling unauthenticated heap use-after-free, memory disclosure and RCE with the web worker's privileges; CVE-2026-109618 reaches RCE as the web worker via an out-of-memory corruption chain.
- Fixed releases named by the PHP project are 8.5.12, 8.4.27, 8.3.36 and 8.2.35, with minimal source backports provided for PHP 7.4, 8.0 and 8.1.
Every PHP setup that handles web requests is impacted by both, PHP-FPM, Apache using mod_php, php-cgi, FrankenPHP and LiteSpeed included, and patches have been released in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, alongside minimal source-level backports targeting PHP 7.4, 8.0 and 8.1.
A machine summary written from the reports listed below; read them for the full account. How summaries are made and what is checked.
Who reported it, and when?
A report's title is shown once our automated legal check has read it and passed it; 12 reports are named by outlet, and the links lead to each report.
Who was named?
- PHP
- PHP2Shell
- CVE-2026-109619
- CVE-2026-109618
- php-cgi
- PHP security team
- PHP-FPM
- LiteSpeed
- FrankenPHP
More news naming PHP
Sources: the outlets' reports linked on this page; counts and times from GetYourBrief's record of those reports (methodology).