VulnerabilityPublished 10 Feb 2026

CVE-2026-23686: SAP NetWeaver Application Server Java · HTTP Request/Response Splitting

Affects SAP NetWeaver Application Server JavaSource CVE Database V5

Not known to be exploited · CVSS 3.4 Low.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

3.4Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SAP_SESAP NetWeaver Application Server Java	Affected =LMNWABASICAPPS 7.50	Fixed in–

AI-suggested

Restrict administrative access strictly to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of privilege misuse.
Monitor and audit administrative actions within SAP NetWeaver environments to detect unusual configuration changes promptly.
Apply SAP security patches and updates as soon as they become available for this vulnerability to ensure the underlying flaw is remediated.
Implement input validation and sanitization controls at the application layer to neutralize CRLF sequences in HTTP headers and other inputs.
Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious header injection attempts.
Conduct regular security assessments and penetration testing focused on SAP NetWeaver configurations to identify and remediate injection weaknesses.
Educate administrators on secure configuration management practices and the risks associated with CRLF injection attacks.
Consider network segmentation to isolate SAP NetWeaver servers from less trusted network zones, limiting exposure to potential attackers.

Description

CVE-2026-23686 is a CRLF injection vulnerability in SAP NetWeaver Application Server Java affecting version LMNWABASICAPPS 7.50. An authenticated attacker with administrative privileges can inject specially crafted content into HTTP headers, leading to improper neutralization of CRLF sequences. This allows manipulation of application-controlled settings through injection of untrusted entries in generated configuration. The vulnerability impacts integrity with low severity, while confidentiality and availability remain unaffected. Exploitation requires high privileges and user interaction, limiting the attack scope. No known exploits are reported in the wild. European organizations using this SAP product should prioritize patching and restrict administrative access to mitigate risk. Countries with significant SAP enterprise deployments and critical infrastructure reliance on SAP NetWeaver are most likely affected.

Impact

For European organizations, the primary impact of CVE-2026-23686 is the potential unauthorized modification of application configuration settings within SAP NetWeaver Application Server Java environments. While confidentiality and availability are not affected, integrity compromises can lead to misconfigurations that may degrade application reliability or introduce secondary vulnerabilities. Organizations relying heavily on SAP NetWeaver for critical business processes, especially in sectors like manufacturing, finance, and utilities, could face operational disruptions or compliance issues if attackers manipulate configurations. The requirement for administrative access limits the threat to insider threats or attackers who have already breached perimeter defenses. However, given SAP's widespread use in Europe, even low-severity integrity issues warrant attention to maintain trustworthiness of enterprise applications and avoid cascading effects in complex IT environments.

Summary

CVE-2026-23686 is a vulnerability classified under CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers) found in SAP NetWeaver Application Server Java, specifically version LMNWABASICAPPS 7.50. The flaw arises because the application fails to properly sanitize carriage return and line feed (CRLF) characters in HTTP header inputs submitted by authenticated users with administrative privileges. An attacker exploiting this vulnerability can craft malicious input that injects additional HTTP header entries or manipulates existing configuration settings generated by the application. This injection can alter application-controlled parameters, potentially leading to unauthorized changes in application behavior or configuration. However, the impact is limited to integrity, with no direct effect on confidentiality or availability. The vulnerability requires an attacker to have high-level privileges (administrative access) and involves user interaction, which reduces the likelihood of widespread exploitation. The CVSS v3.1 base score is 3.4, reflecting low severity due to the limited impact and exploitation complexity. No public exploits have been reported, and no patches are currently linked, indicating that mitigation may rely on SAP updates or configuration hardening. This vulnerability highlights the importance of proper input validation and neutralization of CRLF sequences in HTTP headers to prevent injection attacks that can compromise application integrity.

CWE-113Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') (opens in a new tab)
Variant weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.
Implementation · Input Validation
Construct HTTP headers very carefully, avoiding the use of non-validated input data.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. If an input does not strictly conform to specifications, reject it or transform it into something that conforms.
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
HTTP Request Splitting (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
HTTP Response Splitting (opens in a new tab)
AJAX Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Feb 2026, 09:37 UTC

WeaknessesCWE-113

Technical details

References

Community reviews

Related threats