Actively exploited PHP memory corruption flaw enables unauthenticated remote code execution
CISA added CVE-2026-109618, a PHP memory corruption flaw allowing unauthenticated remote code execution, to its Known Exploited Vulnerabilities catalog on 26 October 2026. Anyone running PHP-based web servers or applications is concerned, and US federal agencies must act by 29 October.
What to do now
- Product
- PHP (PHP Group)
- Affected versions
- Versions not specified in the source
- Fixed in
- Not specified in the source; check php.net
- CVE
- CVE-2026-109618
On 26 October 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) listed CVE-2026-109618 in its Known Exploited Vulnerabilities catalog. The flaw affects PHP, the scripting language maintained by the PHP Group and found on a large share of web servers. CISA describes it as a memory corruption issue that lets an unauthenticated attacker run code remotely.
The weakness categories attached to the entry point to several memory-handling problems: use after free (CWE-416), improper handling of exceptional conditions (CWE-755), access of an uninitialized pointer (CWE-824), improperly controlled sequential memory allocation (CWE-1325) and incorrect initialization of a resource (CWE-1419). The source does not explain the exact exploitation path or which PHP functions are involved.
CISA notes that the flaw sits in an open-source component that may be bundled into many third-party products. Organisations therefore need to look beyond their own PHP installs to appliances, packaged software and container images that ship the interpreter. The agency also points to an alert it issued on 21 October 2026 titled "Critical vulnerabilities in PHP require immediate patching".
The catalog entry does not list affected or fixed versions, so administrators should rely on the advisories published on php.net. CISA also states that it is unknown whether the flaw has been used in ransomware campaigns.
US federal agencies have until 29 October 2026 to apply vendor mitigations under Binding Operational Directive 26-04. Unusually, the entry is flagged for forensic triage, meaning patching alone is not enough and systems should be examined for signs of prior compromise. Where no mitigation is available, the directive calls for discontinuing use of the product.
What to do now
- Inventory every server, application, appliance and container image that includes PHP, starting with internet-facing systems.
- Apply the fixes or mitigations published by the PHP Group on php.net, since the source does not name fixed versions.
- Check exposed systems for signs of compromise such as unexpected processes, modified web files or unusual outbound connections, in line with CISA's forensic triage requirement.
- Ask vendors of third-party products that embed PHP whether they are affected and when an update will ship.
- If a fix cannot be applied quickly, isolate affected systems or take them off the internet, as CISA advises.