Cyber Resilience

CVE-2026-7263

DoS in Php 8.4.0 – 8.4.21

Published
10 May 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:M/U:Amber
EPSS Score 0.0035 28th percentile
Risk Priority 40 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-7263 is a medium-severity Improper Resource Shutdown or Release (CWE-404) vulnerability in Php Php. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In PHP versions 8.4.* before 8.4.21 and 8.5.* before 8.5.6, DOMNode::C14N() method may process the XML data incorrectly, causing a circular linked list in the data structure representing the XML document. This may cause subsequent processing of the XML document…

more

to enter infinite loop, causing denial of service in the processing application.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1499.001 OS Exhaustion Flood Impact
Adversaries may launch a denial of service (DoS) attack targeting an endpoint's operating system (OS).
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1735Same product: Php Php
CVE-2023-0568Same product: Php Php
CVE-2023-0662Same product: Php Php
CVE-2024-2757Same product: Php Php
CVE-2026-7259Same product: Php Php
CVE-2025-6491Same product: Php Php
CVE-2025-14180Same product: Php Php
CVE-2026-7262Same product: Php Php
CVE-2016-3078Same product: Php Php
CVE-2026-6722Same product: Php Php

Affected Assets

php
php
8.4.0 — 8.4.21 · 8.5.0 — 8.5.6

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect resource releases after code is written.

Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.

Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.

Engineering principles can require explicit resource acquisition/release patterns that stop improper shutdown from being introduced.

Priority-based resource allocation limits the blast radius when released resources are not returned to the pool.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly include coding standards for correct resource allocation and release.

DE.CM-09 partial match
prevents

Runtime monitoring can detect resource exhaustion caused by improper shutdown or release.

ID.AM-08 partial match
prevents

Lifecycle management of assets can encompass proper resource release at end-of-life or shutdown.

ID.RA-01 partial match
prevents

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

PR.IR-04 partial match
prevents

Capacity management helps surface leaks from unreleased resources but does not prevent the coding flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can uncover infinite-loop conditions before release.

prevents

Including restart, recovery and media-handling instructions reduces the likelihood that resources or sensitive data will be left in an exposed or improperly released state after a failure.

prevents

Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.

prevents

Application security requirements can specify loop-termination rules, indirectly reducing the weakness.

prevents

Secure coding standards directly address loop termination and prevent infinite loops.

References