PHP maintainers knew of memory-handling flaw two years before public disclosure
Operators running end-of-life PHP versions now have patches reaching back to 7.4, and most installations online are on unsupported releases.
Operators running end-of-life PHP versions now have patches reaching back to 7.4, and most installations online are on unsupported releases.
Operators of internet-exposed management interfaces and Active Directory environments face the most immediate risk, with federal agencies facing a fixed patch deadline.
Federal agencies have until October 29, 2026 to patch, and tens of millions of PHP services still run a vulnerable version.
Many sites were running end-of-life PHP versions, so the one-point-release fix could not be applied quickly everywhere.
Operators running unpatched PHP are exposed, and a further flaw has no patch yet, only a configuration workaround.
Operators running any unpatched PHP since version 5.4 are exposed, and the advisories say updating and restarting every worker is the only safe fix.
The bugs remain unexploited so far, but AI is shortening the time between disclosure and attack for under-resourced teams.
Sites running PHP have less time to patch than planned, after a leaked embargo put details of two 9.2-rated runtime bugs into circulation early.
Defenders should not treat the public disclosure date as the earliest point at which the flaws were exploited.
Millions of exploit attempts have been logged, but it is unclear whether any attack has succeeded, and only the latest PHP release carries the fix.
Operators running PHP 8.1 or older have no official fix and must move to a supported branch.
Operators running PHP 8.1 or older face the most pressing risk, since no official fix is coming for those versions.
Affected servers need patches for a PHP bug, and some certificates from one authority may still be trusted by a macOS utility.
Operators running PHP on public sites face urgent patching, and no temporary workaround fully blocks the attacks.