Google warns fully automated AI-driven attacks are close, shrinking time to patch
Attackers are already using multi-agent AI to find and exploit flaws, leaving defenders less time to respond.
Attackers are already using multi-agent AI to find and exploit flaws, leaving defenders less time to respond.
Organizations running affected Check Point appliances face a destructive attack in two waves, with the second reaching several countries.
Operators running end-of-life PHP versions now have patches reaching back to 7.4, and most installations online are on unsupported releases.
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.
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.
Railway has paused deployments and begun restoring builds, starting with Pro and Enterprise workspaces, while it investigates the incident.
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.
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.