Servers running affected Linux kernels can be taken over as root by attackers who combine the flaw with PHP weaknesses, so patching is the immediate step.
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 industrial control systems now have to check which vendor products carry the PHP engine flaws, several of which still lack full patches.
Operators running unpatched PHP are exposed, and a further flaw has no patch yet, only a configuration workaround.
Organisations running unpatched PHP servers face active exploitation, and defenders are being told to watch for a specific pattern of errors in their logs.
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.
Server operators running affected configurations must disable one setting now, while attackers have so far mostly probed the PHP2Shell flaws without confirmed compromises.
Patching is slow for sites on older PHP versions, and an early warning of a working exploit was withdrawn.
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.
Organisations are still checking exposure, and experts warn the fallout may take months to fully emerge.
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.
Sites running PHP may need to take systems offline until fixes are applied, as attackers were already probing the weaknesses before the public warning.
Operators running PHP 8.1 or older face the most pressing risk, since no official fix is coming for those versions.
Operators running PHP on public sites face urgent patching, and no temporary workaround fully blocks the attacks.