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 Frontier AI finds critical flaws faster than maintainers can fix them / R08-2

R08-2: Several finders, one small team

Because Calif, OpenAI, Wiz and a fourth reporter reached the same small security team within weeks, each report costs the same few people triage time, resulting in a coordination load that grows with every AI-assisted finder.

Rating 12 high · Likelihood 4 Likely · Impact 3 Significant · Kind Operational · Acceptance not recorded

Basis. Four credited reporters; dates confirmed.

The path

Told inphp2shell in perspectivephp2shell in perspec…Acted on byCISOCISOHistorianHistorianCarried byThe PHP security team (bearer)The PHP security tea…The finders (source)The finders (source)The PHP Foundation (owner)The PHP Foundation (…RiskR08-2 Several finders, one small teamR08-2 Several finder…Arises fromA 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
The PHP security teambearerTriage for every report.7 risks
The finderssourceEach report is load.7 risks
The PHP FoundationownerDecides how the team is resourced.3 risks

What it arises from

The evidence

ClaimStatusFact-checkSources
The GitHub advisories credit four reporters: lcfr-hax (Calif), sagitzadik-wiz (Wiz), amyb-oai (OpenAI) and tomash-areionconfirmedA6 EstablishedPHP PHP Daubois
Calif found the flaws first: discovery 1 August, hash commitment 5 August, report to PHP 11 AugustconfirmedA3 EchoedCalif Ryan Austin, Calif on X PHP Foundation
OpenAI independently reported the same root cause on 11 August, with further vectors on 18 SeptemberreportedA2 ReportedPHP Foundation PHP
Wiz Research independently discovered the first flaw on 19 August and reported on 24 AugustreportedA2 ReportedWiz PHP Foundation

Treatments

TreatmentStatusWhere
A coalition that pooled reports for one fixpartialWho found php2shell, and what the AI did

The standards that govern it

FrameworkControlWhat it asksFamily
ISO/IEC 29147 and 3011129147:receiptReceiving vulnerability reports and acknowledging the finderPractice and technique
NIST CSF 2.0ID.RA-08Processes for receiving, analysing and responding to vulnerability disclosures are establishedFrameworks and control catalogues
NIST SSDFRV.1Identify and confirm vulnerabilities on an ongoing basisFrameworks and control catalogues

The stories that tell it

On this site: Who found php2shell, and what the AI did