Threats / SAP / CVE-2022-22536
CVE-2022-22536
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
SAP Multiple Products vulnerability
HTTP request smuggling in SAP NetWeaver and related products allows unauthenticated attackers to prepend arbitrary data to victim requests, enabling impersonation and cache poisoning.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can exploit HTTP request smuggling to execute functions as a victim user or corrupt web caches, affecting multiple SAP server products without authentication requirements.
CISA KEV Yes · 2022-08-185EPSS 0.97945 (verify live)6Exploit Public PoC7CVSS 9.8 (CISA)4CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
310 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-08-18).
Probability (EPSS)
EPSS 0.97945 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: SAP, Multiple Products. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-444 HTTP Request Smuggling — weakness family: Web / client.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 190 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malformed HTTP request that exploits request parsing differences between the front-end proxy and back-end SAP server.
Business
The organization's web infrastructure becomes vulnerable to request manipulation without any authentication barrier.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I prepend my malicious payload to a legitimate victim's request, causing the server to process both as a single request under the victim's session.
Business
Attackers can perform unauthorized actions impersonating legitimate users, bypassing access controls and audit trails.
3
Lateral reach — past segmentation narrative 3
Attacker
I inject cache-poisoning payloads that intermediary web caches store and serve to other users visiting the same resources.
Business
The organization's web cache becomes a vector for distributing malicious content to all users, degrading service integrity and user trust.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05