AI Science Tracker

Calif and OpenAI AI-assisted research identifies PHP out-of-memory remote code execution

PHP runtime request parsing and shutdown paths · AI involvement attributed to Calif researchers’ LLM companion; OpenAI attributes GPT-5.6 Sol to Calif’s critical finding (exact model-to-finding mapping not independently detailed in the researcher post)

Finding and attribution

A controllable out-of-memory failure during request parsing could leave PHP request state incompletely initialized; request shutdown could later treat that state as valid, enabling remote code execution under confirmed mod_php conditions. The same underlying issue also has conditional paths on other SAPIs, as described by the maintainer advisory.

Product: PHP runtime request parsing and shutdown paths. AI system: Calif researchers’ LLM companion; OpenAI attributes GPT-5.6 Sol to Calif’s critical finding (exact model-to-finding mapping not independently detailed in the researcher post). Team / organization: Calif, OpenAI Patch the Planet, PHP Project.

CVE identifiers: CVE-2026-109618.

AI and human contribution (source account): OpenAI states Calif identified a critical PHP flaw using GPT-5.6 Sol. Calif’s first-party research account describes asking an LLM companion to help find controllable OOM/fatal behavior, then an AI agent tracing an initialization-order defect during source review; this discovery path is mapped here to the PHP maintainer’s CVE-2026-109618 OOM-corruption issue. The mapping between OpenAI’s model attribution and this specific CVE is an inference from the matching OOM description and the researcher timeline; OpenAI’s statement itself does not name the CVE. PHP’s advisory credits multiple reporting teams, so no priority claim is made.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: Calif reports coordinated disclosure; OpenAI says the coalition prepared fixes before public disclosure. No claim of exploitation in the wild is made here.

Remediation status: fix documented. PHP fixed in 8.2.35, 8.3.36, 8.4.27 and 8.5.12; older branches may depend on distribution/support-vendor backports. The advisory warns that `memory_limit=-1` is only partial mitigation and workers must be restarted after changes. Deployment is not verified.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 21 Oct 2026. AI attribution dated 21 Oct 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Critical · highest recorded score 9.2. Documented technical effects: code execution.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-109618: CVSS 4.0 · 9.2 (Critical) · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · Assessment scenarios: GENERAL. php (CNA; CVE Program record) · checked 16 Nov 2026.

CVE-2026-109618: code execution.
Prerequisites / affected scope: CNA description: PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE)..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: PHP fixed in 8.2.35, 8.3.36, 8.4.27 and 8.5.12; older branches may depend on distribution/support-vendor backports. The advisory warns that `memory_limit=-1` is only partial mitigation and workers must be restarted after changes. Deployment is not verified.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases