Critical PHP2Shell Exploit Code Goes Public as Hackers Attempt to Deploy Botnet Malware
Public exploit code for critical PHP vulnerabilities PHP2Shell (CVE-2026-109618, CVE-2026-109619) released; attackers
Public proof-of-concept code for two critical PHP vulnerabilities, collectively known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), has been released. Attackers have attempted to leverage these flaws, which allow unauthenticated code execution, to deploy botnet malware, specifically a Mirai variant named Potassium. While Sophos observed scanning and failed exploit attempts, they found no evidence of successful compromise.
AI summary of the linked source. Not reviewed by an editor. How this works
Run PHP?
Get an email when a new story names PHP, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonTwo critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619), allowing unauthenticated remote code execution, were quickly weaponized after proof-of-concept exploit code was made publicly available. Attackers wasted no time attempting to deploy a Mirai-variant botnet (Potassium) against unpatched internet-facing PHP systems. The window between public PoC release and active exploitation attempts was extremely short, highlighting that once exploit code is public, organizations have little time to react. While no successful compromises were confirmed in this instance, the incident underscores the critical importance of proactive patch management and continuous vulnerability monitoring for externally exposed services.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Threat intelligence
Attack campaigns reach your sector, suppliers or software before your team hears about them.
Indicators of Compromise
Extracted by AI from the linked source. Not reviewed by an editor. How this works
- cve — CVE-2026-109618
- cve — CVE-2026-109619
- malware — Potassium
- malware — Mirai