PHP2Shell flaws were targeted before patches, triggering global security rush
publishers 21articles 21first reported 22 Oct, 02:24 UTCdeveloping since 22 Oct · 8 editions
Hackers attempted to exploit two critical PHP vulnerabilities four days before patches were publicly released, according to Amazon Web Services, as governments and companies rushed to secure websites and online services.
AWS said its MadPot honeypot detected an attempt targeting the flaws, collectively called PHP2Shell, on October 17 from an address linked to a commercial anonymization network. Additional attempts appeared in the hours before the October 21 disclosure, and AWS said the vulnerabilities are now being “broadly exploited in the wild.” It remains unclear how the earlier actor learned of the flaws or whether those attempts succeeded on real systems.
The vulnerabilities, CVE-2026-109618 and CVE-2026-109619, could allow unauthenticated attackers to execute malicious code remotely on vulnerable servers. The PHP Foundation said details leaked before fixes were released. Executive director Elizabeth Barron told The Verge that the foundation knew of no successful remote-code-execution attack but called immediate updates imperative.
Cloudflare reported that exploitation attempts rose from thousands before the announcement to millions afterward. Governments and businesses temporarily suspended some websites and services while applying patches, including organizations in Japan and Europe.
The FBI, the US National Security Agency and Singapore’s cybersecurity authorities urged organizations to update affected PHP installations immediately. The FBI advised taking systems offline if they cannot be patched, monitoring for unusual PHP processes, isolating compromised machines and preserving server logs for investigation.
HOW THIS STORY WAS MADE
Written from 8 articles, 5 with the publisher's own text; 8 independent newsrooms once syndicated copies count as one; this version written 12 h after the record first saw the story; the editor kept it as written.
- Publishers
- 21
- Source articles
- 21
- Given to the writer
- 8, 5 with the article's own text
- Independent newsrooms
- 8
- This version written
- 12 h after the record first saw the story
- Second model (editor)
- kept as written
- Publication gate
- passed
- Human review
- none
WHAT THE EDITOR DID
The second model checked the writer's draft against the same sources and published it as written.
Written by a language model from the sources above, then checked by a second model that may only cut, attribute or correct. How it works →