PHP2Shell exposes critical PHP flaws
Kinsta spotted attack attempts against CVE-2026-109618 and CVE-2026-109619 starting Oct. 21. They affect cloud sites running vulnerable PHP.
Starting on Oct. 21, 2026, requests designed to exploit two critical PHP vulnerabilities were observed, later identified as CVE-2026-109618 and CVE-2026-109619. Kinsta warned that, under certain conditions, they could allow unauthenticated remote code execution and affect websites hosted in cloud infrastructure running vulnerable PHP versions.
Starting Oct. 21, 2026, researchers observed requests designed to exploit two critical PHP vulnerabilities, later identified as CVE-2026-109618 and CVE-2026-109619. Kinsta said that, under certain conditions, they could allow unauthenticated remote code execution and affect websites hosted on cloud infrastructure running vulnerable versions of PHP.
What do these flaws describe?
White Knight Labs said CVE-2026-109618 is a memory corruption issue tied to out-of-memory error handling in multipart requests. The same technical research identified CVE-2026-109619 as a use-after-free caused by stale global state between requests handled by the same worker process. In practical terms, these are two separate paths to possible compromise of an exposed service.
What did vendors and analysts say?
TXOne Networks said its Safe Lock TXOne Edition product was potentially affected by CVE-2026-109618, but not by CVE-2026-109619, and recommended updating PHP to the patched versions. Hillstone, meanwhile, said exploitation of CVE-2026-109619 requires the attacker to be able to reach the device's web administration page over the network, a detail that limits practical scope compared with indiscriminate exploitation of any PHP installation.
CyberSecureFox said scan and exploitation attempts had been observed within hours of disclosure, although it also clarified that Sophos, Arctic Wolf and Hunt.io had not confirmed any compromises stemming from those attempts. That leaves the focus on opportunistic activity around the announcement, rather than a closed attribution of confirmed incidents.
What does the cloud context show?
CISOCLUB reported that a SANS survey placed misconfigurations at 45% of reported critical incidents and credential theft at 22%. The same reference added that 49% of organizations take more than 24 hours to resolve a known critical breach, a figure that helps explain why an exploitable flaw in cloud-deployed components can escalate quickly.
In parallel, an InfraStack report, which attributes the information to Google Threat Intelligence, said LLMjacking groups carried out intrusions in 2026 across South America, North America and Asia-Pacific. According to that report, the actors used stolen cloud keys and tokens to consume services such as AWS Bedrock, Google Gemini and Azure OpenAI, along with IAM credentials and exposed or compromised Google Cloud service account keys. The available regional evidence remains limited, however, and still needs validation through primary Google Threat Intelligence reporting, cloud providers or national CERTs.
Was there a PHP attack?
Yes, requests and exploitation attempts against PHP were observed starting Oct. 21, 2026, but the body does not confirm that they led to broad compromises. The available signal points to scanning activity and opportunistic exploitation against installations running vulnerable PHP.
Kinsta said those attempts were aimed at CVE-2026-109618 and CVE-2026-109619. CyberSecureFox added that exploitation attempts were seen within hours of disclosure, although Sophos, Arctic Wolf and Hunt.io did not confirm any compromises tied to that activity.
Sources
- Impact Analysis of PHP2Shell on Safe Lock TXOne Editionhelp.txone.com· TXOne Networks
- LLMjacking crews (UNC6993, Jet Night) use stolen cloud keys and tokens to run up AWS Bedrock, Gemini and Azure OpenAI bills of $100K+/day and resell the access (Google GTIG)infrastack.ai· InfraStack
- Exploiting PHP Foundational Vulnerabilitieswhiteknightlabs.com· White Knight Labs
- Multiple Products Third-Party PHP Component Remote Code Execution Vulnerabilityhillstonenet.com· Hillstone Networks
- Encuesta de SANS revela una brecha preocupante: ¿por qué las empresas siguen sin estar preparadas para proteger la nube?cisoclub.mx· CISOCLUB
- PHP2Shell: Mass Exploitation Attempts And The Potassium Botnetcybersecurefox.com· CyberSecureFox
- Los entresijos del lanzamiento del parche de emergencia PHP2Shell de Kinstakinsta.com· Kinsta


