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 / R09

R09: Not knowing where PHP runs

Because PHP sits in appliances, images, plugins and forgotten sites, an organisation cannot patch what it has not listed, resulting in an update programme that reports done while vulnerable runtimes remain.

Rating 16 high · Likelihood 4 Likely · Impact 4 Major · Kind Operational · Acceptance not recorded

Basis. 418 inventory rows under investigation; the precedent of every component flaw since Log4Shell.

The path

Told inExposed is not exploitedExposed is not explo…Acted on byCTOCTOPlatform engineers and developersPlatform engineers a…Story site agentStory site agentCarried byCTO (owner)CTO (owner)Platform engineers and developers (treater)Platform engineers a…Suppliers in the NCSC-NL inventory (informer)Suppliers in the NCS…RiskR09 Not knowing where PHP runsR09 Not knowing wher…Arises fromNot knowing where PHP runsNot knowing where PH…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
CTOownerOwns the inventory.3 risks
Platform engineers and developerstreaterBuild it and keep it.4 risks
Suppliers in the NCSC-NL inventoryinformerSay which products embed PHP.3 risks

What it arises from

The evidence

Treatments

TreatmentStatusWhere
A software inventory with component versions (SBOM)partialIf you run PHP: the steps, in order, with their sources

The standards that govern it

FrameworkControlWhat it asksFamily
NIST CSF 2.0ID.AM-02Inventories of software, services and systems are maintainedFrameworks and control catalogues
NIST SP 800-53CM-8System component inventoryFrameworks and control catalogues
CIS Controls16.4Establish and manage an inventory of third-party software componentsFrameworks and control catalogues
DORAArt.8Identification of ICT assets, their dependencies and the risks to themLaw and regulation
ISO/IEC 27001A.8.9Configuration managementManagement-system standards
Cyber Resilience ActAnnexI.IIVulnerability handling requirements: identify components, remedy without delay, publish fixed vulnerabilities, coordinated disclosureLaw and regulation

The stories that tell it

On this site: If you run PHP: the steps, in order, with their sources · The NCSC-NL inventory: 674 products