Vulnerability detailsExploited

Severity
9.2 Critical · CVSS 4.0 · Php
Exploited
Since 2026-10-26 (CISA)
CISA deadline
2026-10-29
Published
PHP Group PHP

Affected: 8.2.* to before 8.2.35; 8.3.* to before 8.3.36; 8.4.* to before 8.4.27; 8.5.* to before 8.5.12

Fixed: 8.2.35; 8.3.36; 8.4.27; 8.5.12

github.com · CVE record · NVD

Stories

  1. Image: The New Stack

    Chainguard defends its choice to break the PHP security embargo: “We own the decision.”

    Chainguard CTO Matt Moore defended at KubeCon + CloudNativeCon North America 2026 the company's release of patched PHP container images more than six hours before the October 21 coordinated disclosure lifted. PHP maintainers accused Chainguard of giving attackers a head start, but Moore said the company believed attackers could already exploit, or were close to exploiting, CVE-2026-109618 and CVE-2026-109619, citing security vendors' reports of activity. "We own the decision," he said.

  2. Siemens Building Automation and Energy Products

    Siemens has issued an advisory on how the "php2shell" flaws affect its building automation and energy products. The two critical, unauthenticated remote code execution vulnerabilities in the PHP runtime, CVE-2026-109618 and CVE-2026-109619, were disclosed on October 21, 2026. Siemens has released new versions of several affected products, is preparing further fixes, and recommends updating and restricting network access while its assessment continues.

  3. Siemens RUGGEDCOM APE1808

    Siemens has warned that all versions of its RUGGEDCOM APE1808 are affected by the PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619 through Palo Alto Networks' PAN-OS, rated CVSS v3 9.8. One flaw stems from PHP's longjmp() out-of-memory handling leaving request memory uninitialized, which can lead to remote code execution. Customers are told to apply workarounds from Palo Alto Networks' upstream notices.

  4. Image: MariaDB Foundation

    Still on MariaDB 10.6? Why your next upgrade is a security decision

    The item urges users still running MariaDB 10.6 to treat their next upgrade as a security decision. It links the warning to emergency PHP fixes shipped on 21 October 2026 for two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619, collectively called PHP2Shell. The summary says exploit details leaked before the patches and attacks began within hours; it says upgrading PHP or shutting it down was the only real fix.

  5. Image: BleepingComputer

    CISA confirms active exploitation of PHP2Shell flaws and orders federal agencies to patch

    CISA confirmed active exploitation of the two PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619, by adding them to its Known Exploited Vulnerabilities catalog. Both flaws carry a CVSS score of 9.2 and can enable unauthenticated remote code execution on affected PHP servers. Federal civilian agencies must patch by October 29, while researchers have also documented successful exploitation. Patches were released on October 21, and attackers reportedly attempted exploitation before public disclosure.

  6. PHP2Shell and Azure DevOps: what to check

    Microsoft said Azure DevOps Services and Azure DevOps Server do not use PHP to handle customer requests, so the two critical PHP vulnerabilities disclosed on October 21, 2026, do not affect those products directly. PHP runtimes used in pipelines, containers, and deployed applications still need separate patching. Microsoft maintains the cloud service, while customers are responsible for PHP in their own pipeline steps, images, applications, or server hosts.

  7. Image: Tom's Hardware

    Bitcoin reward offered to anyone who could break into an unpatched server running PHP, hacker cracks site and claims bounty

    A hacker breached a vulnerable server running PHP and claimed a Bitcoin bounty worth $2,021.22, ending a challenge set up to test how readily critical software flaws could be exploited. The prize had grown from about $502 to 0.02511679 BTC through donations, and the successful claim was recorded at 15:47 UTC on October 25, roughly 19.28 hours after the challenge began. The experiment followed disclosure of two critical PHP vulnerabilities, for which fixes had been released on October 21.

  8. Image: The New Stack

    PHP2Shell was only the beginning: AI is accelerating the patch race

    Organizations across Europe and elsewhere took public services offline after the disclosure of two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. The PHP project released fixes for all community-supported versions on October 21, after government agencies and businesses had taken precautionary measures while awaiting mitigation. The account warns that an estimated 40% of PHP users run unsupported versions, leaving a broader patching challenge as AI accelerates vulnerability discovery.

  9. PHP2Shell and eMudhra Patched

    Docker Hardened Images published a rebuilt, patched PHP image on October 22, within 24 hours of the upstream release. The update addresses PHP2Shell, a pair of critical PHP engine flaws that can let unauthenticated requests execute code on servers; PHP is used by about 69% of websites with a known server-side language. The item also describes an eMudhra certificate compromise involving eight intermediate certificates whose private keys could be computed from their public certificates, allowing certificates for any website to be issued and accepted.

  10. Image: Tom's Hardware

    Consultant comes clean for sparking worldwide panic by accidentally breaking the PHP vulnerability embargo

    A self-employed consultant apologized on Hacker News after posting about two upcoming PHP vulnerabilities before their disclosure embargo. The user said they had not known about the news blackout and shared the vulnerability identifiers to alert people who follow PHP’s four-week release cycle. They accepted responsibility, saying the post disrupted the coordinated disclosure schedule and created extra work.

  11. Image: The Register

    PHP2Shell Exploitation Attempts Surge, with Attacks Reported Before Disclosure

    Attackers have launched millions of attempts to exploit the PHP2Shell vulnerabilities, targeting systems for inclusion in a Mirai botnet variant, while Amazon says activity began four days before public disclosure. Cloudflare observed thousands of attempts in the 10 hours before disclosure, rising to tens of thousands within 45 minutes and hundreds of thousands within two hours. One account says observed attempts to deploy the malware were unsuccessful, while another reports exploitation in the wild at scale.

  12. Image: The Register

    PHP2Shell exploit bypasses protections designed to stop remote code execution

    VulnCheck researchers developed an exploit for PHP2Shell that bypasses ASLR, a protection that had been a major barrier to exploiting the flaw on real-world x86-64 servers. The exploit targets CVE-2026-109618, a critical PHP memory-corruption bug that enables remote code execution, and VulnCheck made it available only to its Initial Access Intelligence customers. The PHP Foundation disclosed and patched PHP2Shell flaws CVE-2026-109618 and CVE-2026-109619 on Wednesday, amid reports of attacks before disclosure.

  13. Image: BleepingComputer

    Critical PHP2Shell flaws prompt patches and urgent upgrades

    The PHP project released fixes for two critical remote-code-execution vulnerabilities, PHP2Shell, on October 21, 2026. Identified as CVE-2026-109618 and CVE-2026-109619, the flaws affect PHP versions dating back to 5.4; patched releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The vulnerabilities can affect web servers running PHP, and GitLab says exploitation can occur before application code runs in a confirmed Apache mod_php scenario. Security companies also observed exploitation attempts before patches were released.

  14. Image: Wired

    PHP2Shell exploit attempt detected four days before vulnerabilities were disclosed

    Amazon detected an attempt to exploit the PHP2Shell vulnerabilities on October 17, four days before they were publicly disclosed, using its MadPot honeypot service. The flaws affect PHP, and patches were released on Wednesday. Amazon said exploitation had become broad after the patches were released, while another account describes hackers attempting exploitation before patching began. The detection came from a monitoring system designed to attract or observe attackers.

  15. Image: AppleInsider

    Critical PHP vulnerabilities threaten your NAS, not every vendor has a fix

    Attackers are actively exploiting two critical PHP vulnerabilities to target internet-exposed NAS devices. Tracked as CVE-2026-109618 and CVE-2026-109619, the flaws could let attackers execute code on affected servers without logging in; Amazon detected an attempted exploit on October 17, four days before public disclosure. PHP released security updates on October 21 for versions 8.2 through 8.5, while NAS owners may also need to consider PHP applications running in Docker containers.

  16. Image: The New Stack

    AI found a critical PHP flaw. The bigger failure began in 2024.

    PHP’s release of fixes for two critical flaws prompted some service operators to take websites offline while they waited to patch. The fixed versions are 8.2.35, 8.3.36, 8.4.27 and 8.5.12; older branches require a supported upgrade or a distributor’s backport. The flaws do not require a WordPress update, and the roughly 70% figure for PHP’s reach does not indicate how many sites were vulnerable or compromised. The emergency also sparked a dispute over coordinated disclosure and raised concerns about pressure on open-source maintainers as AI-assisted security work advances.

  17. Image: AWS Security Blog

    Using AWS WAF to apply mitigations for PHP2Shell RCE vulnerabilities (CVE-2026-109618 and CVE-2026-109619)

    AWS updated its PHP application managed rule group to version 2.4, making it the default and adding the PHP2Shell_BODY_Extended rule for CVE-2026-109618. The update also notes that the existing PHP2Shell_BODY rule in version 2.4 and later blocks requests associated with CVE-2026-115560, a separate remote code execution issue affecting applications with session upload progress enabled. AWS recommends keeping that setting disabled until PHP releases a fix; the guidance also covers end-of-life PHP versions and security backports.

  18. Image: The Register

    PHP blames supply chain security biz Chainguard for putting huge chunks of the web at risk

    PHP maintainers say Chainguard disrupted disclosure of two critical PHP vulnerabilities, releasing emergency patches on Wednesday after the flaws began circulating online the previous day. Dubbed PHP2shell, the bugs allow unauthenticated attackers to execute code on servers running PHP, which powers a large part of the web. The maintainers credited researchers at Calif, OpenAI and Wiz with finding the vulnerabilities between August and September; the flaws are tracked as CVE-2026-109618 and CVE-2026-109619.

  19. Image: AWS Security Blog

    Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot

    Amazon Threat Intelligence found a PHP2Shell exploitation attempt in MadPot telemetry on Oct. 17, 2026, four days before public disclosure of CVE-2026-109618 and CVE-2026-109619. The attempt came from an IP address linked to a commercial anonymization network and targeted a honeypot while the vulnerability was under embargo. After disclosure on Oct. 21, Amazon identified multiple proof-of-concept exploits and further attempts from anonymized infrastructure, with differing payloads and infrastructure choices suggesting multiple actors. It remains unclear whether the attempts succeeded.

  20. Image: The New Stack

    AI found flaws in the code behind 70% of the web. The fix took two months.

    Researchers disclosed two critical vulnerabilities in PHP’s core engine on Wednesday, after using AI tools to help find them. Tracked as CVE-2026-109618 and CVE-2026-109619, the flaws are collectively called PHP2Shell and score 9.2 on the CVSS v4.0 severity scale. Calif.io found one with OpenAI’s GPT-5.6 Sol; Wiz independently found both using its Wiz Atlas tool with Google’s Gemini 4 Argon and GPT-5.6 Sol. The discovery also prompted OpenAI to propose a framework for handling flaws uncovered with AI.

  21. Image: Cisco Talos

    PHP patches two critical unauthenticated remote-code-execution flaws

    The PHP project released emergency updates to fix two critical flaws that could let unauthenticated attackers execute code on servers handling web requests. The vulnerabilities affect PHP core and can be triggered before application code runs; the fixes are in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Cisco Talos says it observed exploitation in the wild, while another account says exploit attempts have emerged. The PHP team says updating is required for full protection.

  22. Image: The Register

    PHP releases emergency updates for two critical remote-code-execution vulnerabilities

    PHP developers released security updates for four maintained branches to fix two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, which can enable unauthenticated remote code execution. The project urges users to update immediately; its PHP 8.2 announcement says there are no complete mitigations and updating is the only safe choice. A security publisher reports that authorities warned organizations to patch or consider taking exposed applications offline, while a threat-intelligence executive said exploitation attempts had been observed but had not succeeded at the time of his statement.

  23. Image: Cloudflare Blog

    Cloudflare deploys protections against php2shell vulnerability

    Cloudflare deployed web application firewall protections against php2shell, a pair of PHP vulnerabilities disclosed on October 21 by Calif.io, Wiz, OpenAI and Quarkslab. The flaws affect web servers running PHP 5.4 or later and may enable denial of service, remote code execution or data exposure through specially crafted HTTP traffic. Cloudflare says its rules cover known exploit attempts for customers using PHP’s default upload progress field name; sites that changed it are not covered.

  24. PHP 8.5.12 Released!

    The PHP development team released PHP 8.5.12 as a security update, fixing two critical vulnerabilities that could enable unauthenticated remote code execution. The team urges all PHP 8.5 users to update immediately, saying there are no complete mitigations and updating is the only safe choice. The release includes source downloads and Windows source and binaries.

  25. PHP 8.4.27 Released!

    The PHP development team released PHP 8.4.27 as a security update, fixing two critical vulnerabilities that could enable unauthenticated remote code execution. The team urges all PHP 8.4 users to update immediately, saying there are no complete mitigations and updating is the only safe choice. Source downloads and Windows source and binaries are available with the release.

  26. PHP 8.3.36 Released!

    The PHP development team released PHP 8.3.36 as a security update, fixing two critical vulnerabilities that could enable unauthenticated remote code execution. The team urges all PHP 8.3 users to update immediately, saying there are no complete mitigations and updating is the only safe choice. The release includes source downloads and Windows source and binaries.

Topics

Publishers