Cyber Resilience

CVE-2024-9026

Php 8.1.0 – 8.1.30

Public PoC
Published
08 October 2024
Modified
03 November 2025
Patch / advisory
View advisory
CVSS Score v3.1 3.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0049 40th percentile
Risk Priority 32 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-2024-9026 is a low-severity Improper Output Neutralization for Logs (CWE-117) vulnerability in Php Php. Its CVSS base score is 3.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Indicator Removal (T1070); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

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

OWASP Top 10 for Web (2025)

A09:2025 Security Logging and Alerting Failures

EU & UK References

Vulnerability Data

In PHP versions 8.1.* before 8.1.30, 8.2.* before 8.2.24, 8.3.* before 8.3.12, when using PHP-FPM SAPI and it is configured to catch workers output through catch_workers_output = yes, it may be possible to pollute the final log or remove up…

more

to 4 characters from the log messages by manipulating log message content. Additionally, if PHP-FPM is configured to use syslog output, it may be possible to further remove log data using the same vulnerability.

CWE(s)
CWE-117CWE-158NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1070 Indicator Removal Stealth
Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity.
attack.mitre.org →
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 →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1220Same product: Php Php
CVE-2024-8925Same product: Php Php
CVE-2025-14179Same product: Php Php
CVE-2026-17543Same product: Php Php
CVE-2016-3078Same product: Php Php
CVE-2025-1735Same product: Php Php
CVE-2026-6722Same product: Php Php
CVE-2024-8926Same product: Php Php
CVE-2024-11235Same product: Php Php
CVE-2026-6735Same product: Php Php

Affected Assets

php
php
8.1.0 — 8.1.30 · 8.2.0 — 8.2.24 · 8.3.0 — 8.3.12

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.10

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect output neutralization when log messages are constructed from untrusted input.

SI-10 Information Input Validation good match

Input validation directly requires neutralizing or rejecting malformed characters such as NUL before they reach downstream components.

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 and coding standards directly require output sanitization for logs.

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
finds

Security testing can detect log injection flaws but does not prevent them at the source.

A.8.15 Logging partial match
degrades

Logging control directly requires proper log generation and handling, which mitigates improper output neutralization.

A.8.16 Monitoring activities partial match
finds

Monitoring activities rely on trustworthy logs but do not ensure log message integrity.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC includes coding standards that reduce log-related weaknesses but does not specifically address logging.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for neutralizing dangerous characters such as NUL.

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

Secure architecture principles reduce the likelihood of unsafe data flows but do not prescribe character neutralization.

References