Cyber Resilience

CVE-2026-9658

Published
28 May 2026
Modified
17 June 2026
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.0023 13th percentile
Risk Priority 54 floored blend · peak EPSS

Summary

CVE-2026-9658 is a high-severity HTTP Request/Response Splitting (CWE-113) vulnerability. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 13th 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-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Plack::Middleware::Security::Common versions before 0.13.1 for Perl did not block header injections in request paths. The header injection rule was ineffective at blocking header injections in the request paths unless they were double-encoded, for example, GET /path\r\nHTTP/1.1\r\nHost: secret.example.com Note that it…

more

is unclear whether request paths with CRLF followed by additional headers would be blocked by reverse proxies, or how they would be processed by Plack-based servers.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1674 Input Injection Execution
Adversaries may simulate keystrokes on a victim’s computer by various means to perform any type of action on behalf of the user, such as launching the command interpreter using keyboard shortcuts, typing an inline script to be executed,…
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-27260Shared CWE-790
CVE-2026-11331Shared CWE-790
CVE-2024-6540Shared CWE-790
CVE-2023-45239Shared CWE-790
CVE-2025-0431Shared CWE-790
CVE-2026-2328Shared CWE-790
CVE-2023-22578Shared CWE-790
CVE-2024-31616Shared CWE-790
CVE-2024-47984Shared CWE-790
CVE-2024-43443Shared CWE-790

Affected Assets

Common
inferred from references and description; NVD did not file a CPE for this CVE

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)
  • V3.4.2
  • V4.1.3
  • V1.3.6
  • V4.2.3

Mitigating Controls (NIST 800-53 r5) AI

Input validation stops unneutralized CR/LF characters from being accepted and later emitted in HTTP headers.

Output filtering can neutralize CRLF sequences before they reach HTTP response headers.

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 require input sanitization and header handling that prevent CRLF injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities can surface missing input filters during code or configuration review.

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 in development and acceptance can detect CRLF injection flaws before deployment.

prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection into HTTP headers.

prevents

Application security requirements explicitly call for controls against injection flaws including HTTP header manipulation.

prevents

Secure architecture principles reduce the likelihood of header-splitting vulnerabilities through proper component isolation.

prevents

Secure coding standards require neutralization of CRLF sequences before inclusion in HTTP headers.

A.8.15 Logging none match
none

Logging of HTTP traffic can record header-splitting attempts, aiding detection and forensics.

References