Cyber Resilience

CVE-2026-7258

Memory Safety in Php 8.2.0 – 8.2.21

Memory Safety
Published
10 May 2026
Modified
24 July 2026
Patch / advisory
View advisory
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/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:X/R:X/V:X/RE:X/U:Amber
EPSS Score 0.0034 26th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-7258 is a medium-severity Out-of-bounds Read (CWE-125) vulnerability in Php Php. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 26th 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 SI-2 (Flaw Remediation) and CM-6 (Configuration Settings) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, some functions, including urldecode(), pass signed char to ctype functions (like isxdigit()). On the systems with default signed char and optimized table-lookup ctype functions…

more

- such as NetBSD - this can lead to accessing array with negative offset, which can trigger a denial of service.

CWE(s)
CWE-125

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

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.
attack.mitre.org →
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.
attack.mitre.org →
Why these techniques?

Remote exploitation of PHP input-handling functions (e.g., urldecode) on public-facing servers leads to application DoS via out-of-bounds read.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1499.004 Application or System Exploitation Impactconfidence: HIGH
Out-of-bounds read via signed char in urldecode/ctype functions directly enables remote application DoS on affected systems.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-6104Same product: Php Php
CVE-2025-14177Same product: Php Php
CVE-2026-7259Same product: Php Php
CVE-2026-7568Same product: Php Php
CVE-2026-6722Same product: Php Php
CVE-2026-7262Same product: Php Php
CVE-2026-7261Same product: Php Php
CVE-2025-6491Same product: Php Php
CVE-2026-7263Same product: Php Php
CVE-2024-8929Same product: Php Php

Affected Assets

php
php
8.2.0 — 8.2.21 · 8.3.0 — 8.3.31 · 8.4.0 — 8.4.21

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • CM-6 Configuration Settings
Detect
Catch it (NIST detect / respond)
  • RA-5 Vulnerability Monitoring and Scanning
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-2 Flaw Remediation good match
prevent

Directly requires applying the vendor patches that correct the signed-char handling bug in urldecode/ctype functions before the vulnerable PHP versions can be exploited.

RA-5 Vulnerability Monitoring and Scanning partial match
detect

Requires continuous vulnerability scanning that would identify the affected PHP releases (8.2 < 8.2.31 etc.) on NetBSD or similar platforms.

CM-6 Configuration Settings partial match
prevent

Enforces configuration settings that restrict PHP deployment to known-good, patched versions and disable unnecessary exposure of the affected functions.

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-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

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.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
detects

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References