CVE-2026-23686
Sap Netweaver Application Server Java 7.50
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:NSummary
CVE-2026-23686 is a low-severity HTTP Request/Response Splitting (CWE-113) vulnerability in Sap Netweaver Application Server Java. Its CVSS base score is 3.4 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 6th 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-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6461
Vulnerability Data
Due to a CRLF Injection vulnerability in SAP NetWeaver Application Server Java, an authenticated attacker with administrative access could submit specially crafted content to the application. If processed by the application, this content enables injection of untrusted entries into generated…
more
configuration, allowing manipulation of application-controlled settings. Successful exploitation leads to a low impact on integrity, while confidentiality and availability remain unaffected.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.4.2V4.1.3V1.3.6V4.2.3
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover cases where two products interpret the same inputs or state transitions differently.
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.
Applying security engineering principles during design can require unambiguous protocol and data-format specifications that eliminate divergent interpretations between products.
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.
Secure SDLC practices directly require input sanitization and header handling that prevent CRLF injection.
Correlating logs from multiple products can surface discrepancies caused by interpretation conflicts.
Runtime monitoring of software behavior can detect adverse outcomes stemming from differing interpretations.
Supplier risk assessments can identify products whose differing interpretations create systemic exposure.
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.
Security testing in development and acceptance can detect CRLF injection flaws before deployment.
Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection into HTTP headers.
Application security requirements explicitly call for controls against injection flaws including HTTP header manipulation.
Secure architecture principles reduce the likelihood of header-splitting vulnerabilities through proper component isolation.
Secure coding standards require neutralization of CRLF sequences before inclusion in HTTP headers.
Logging of HTTP traffic can record header-splitting attempts, aiding detection and forensics.