PHP2Shell: two critical flaws in the PHP engine are named, numbered and patched
Large-scale supply chain: flaw in a shared component21 October 2026
Two critical flaws in the PHP engine, present since 2012 and reachable in default configurations, were given CVE numbers and fixed in four releases on the same day. It is the reporting system working as designed: one product, known versions, one fix.
- Position
- The PHP engine underneath a large share of the web’s server-side applications
- Reach
- PHP 5.4 and later in default configurations; applications built on it are affected whatever their own code does
What happened
On 21 October 2026 the PHP project released versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12 to fix two flaws, CVE-2026-109618 and CVE-2026-109619, both rated 9.2. Each is a memory-handling error in the PHP engine that can let a remote attacker run code on the server, and the first can also leak memory holding passwords, session tokens and keys. The vulnerable code dates to PHP 5.4.0, released in 2012, and is present in default configurations. Researchers at Calif, Wiz and OpenAI reported the flaws from August onward. Details leaked the day before the release, and Cloudflare reported early attack attempts some hours before the fixes were published.
Sansec, which follows attacks on online stores, wrote that mass exploitation looked less likely than it first expected, because the public exploit code did not work against a default installation and most of it needed a second weakness in the application. Its advice was to update PHP anyway, since the flaws sit in the engine and cannot be fixed in an application's own code.
The ATG nexus
PHP2Shell is on this timeline as the contrast. Everything the vulnerability reporting system needs was present: one product, a list of affected versions, a fix, and servers whose version can be checked. The flaws got numbers, and administrators got something to do.
Attack the Glass has none of those. There is no single product, version or fix to name, so there is nothing to file, and the FAQ and the video linked below set out why. PHP2Shell also repeats what Log4Shell showed in 2021: free code underneath a large part of the internet, carrying a serious flaw for fourteen years before anyone reported it.
Limits of the comparison
This is a server-side flaw with a patch, not a supply-chain event, and it has no bearing on what renders on a screen. How widely it was exploited was not established when this page was written, and the account here rests on one research firm's summary.
On this site
- FAQ: Why is there no CVE?
- Video: A Cyber Threat of a New Kind
- Whitepaper, Chapter 14: Existing Defenses
- Concept: The Open-Source Open Door
- Concept: The Endemic Flaw
- Concept: The Cost of Free