Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?

Risks / R08

R08: Frontier AI finds critical flaws faster than maintainers can fix them

Because four parties, several using frontier models, found the same engine flaws within weeks, and the same capability is open to attackers, the next critical bug in widely used C code may be found by someone who will not report it, resulting in flaws exploited before any embargo exists.

Rating 20 critical · Likelihood 4 Likely · Impact 5 Severe · Kind Strategic · Acceptance not recorded

Basis. AI-assisted discovery reported by the finders and by Chainguard; 'ahead of attackers' is disputed.

The path

Told inphp2shell in perspectivephp2shell in perspec…Acted on byCISOCISOHistorianHistorianCarried byOpenAI (Patch the Planet) (owner)OpenAI (Patch the Pl…The finders (treater)The finders (treater…The PHP project (bearer)The PHP project (bea…Everyone with PHP in the path (bearer)Everyone with PHP in…CISO (bearer)CISO (bearer)RiskR08 Frontier AI finds critical flaws faster than maintainers can fix themR08 Frontier AI find…Arises fromFrontier models that find memory-safety bugs in widely used CFrontier models that…A small, thinly funded maintainer team at the base of the webA small, thinly fund…VulnerabilityCVE-2026-109618CVE-2026-109618CVE-2026-109619CVE-2026-109619Fixed byA soft memory limit that no longer jumpsA soft memory limit …A hard limit that ends the process cleanlyA hard limit that en…An orderly unwind at the next safe pointAn orderly unwind at…Allocations that may fail instead of abortAllocations that may…Request globals reset so nothing survives a failureRequest globals rese…Bounded, deduplicated request parsingBounded, deduplicate…CodeZend/zend_alloc.cZend/zend_alloc.cZend/zend_execute_API.cZend/zend_execute_AP…Zend/zend_hash.cZend/zend_hash.cZend/zend_string.cZend/zend_string.cZend/zend_types.hZend/zend_types.hext/session/session.cext/session/session.…main/SAPI.cmain/SAPI.cmain/main.cmain/main.cmain/rfc1867.cmain/rfc1867.c
The risk sits in the middle. To its left, the stories that tell it, the roles and team members that act on it, and every stakeholder that carries part of it. To its right, what it arises from, the vulnerability behind that, the part of the fix that addresses it and the code the fix changed. Every line is an edge in the graph; every node is a link; hover for the full name. Vulnerabilities, stories and team members include those of the risk this one is part of; roles include those of the risks above and beneath it.

Who carries it

One risk, assigned to every stakeholder that carries part of it, with the part each plays.

StakeholderPartWhyIts register
OpenAI (Patch the Planet)ownerA provider of a general-purpose model with systemic risk, under the EU AI Act.1 risk
The finderstreaterReport what they find.7 risks
The PHP projectbearerReceives the reports.11 risks
Everyone with PHP in the pathbearerEvery user of open-source C.34 risks
CISObearerThe next flaw may arrive with no embargo and no advisory: plans that assume a warning stop working.2 risks

The risks this one is made of

What it arises from

The evidence

Treatments

TreatmentStatusWhere
Coordinated reporting by the model providers (Patch the Planet)partialWho found php2shell, and what the AI did

The standards that govern it

FrameworkControlWhat it asksFamily
EU AI ActArt.55Providers of general-purpose models with systemic risk: evaluate, mitigate systemic risks, report serious incidents, protect cybersecurityLaw and regulation
NIST AI RMFGOVERN-6.1Policies address AI risks from third-party entitiesFrameworks and control catalogues
NIST AI RMFMEASURE-2.7AI system security and resilience are evaluated and documentedFrameworks and control catalogues
ISO/IEC 420016.1.2AI risk assessmentManagement-system standards

The stories that tell it

On this site: Who found php2shell, and what the AI did · In context: php2shell against Kaminsky, Heartbleed, Shellshock, Log4Shell and the last PHP RCE