CVE-2026-76964: ICM2SHELL / SAPBleed in SAP NetWeaver AS ABAP ICM
CVE-2026-76964 is a pre-authentication memory-corruption vulnerability in the Internet Communication Manager (ICM) of SAP NetWeaver Application Server ABAP. Insufficient validation of WebSocket control-frame size and length parameters allows specially crafted traffic to trigger a heap out-of-bounds write and corrupt per-connection state. Exploitation can enable process-memory disclosure, arbitrary code execution, or service termination. The vulnerability is the ICM member of the pair known as ICM2SHELL and SAPBleed; the separate Web Dispatcher vulnerability is CVE-2026-89126. Affected kernel release branches include 7.53, 7.54, 7.77, 7.93, 9.16, 9.18, and 9.20, subject to installed patch levels. SAP NetWeaver AS Java is not affected by this CVE.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can fully compromise the affected SAP system, with high confidentiality, integrity, and availability impacts. Arbitrary commands execute under the ICM operating-system account, typically the SAP installation owner, rather than automatically granting root privileges. Demonstrated memory disclosure exposed TLS private keys, valid MYSAPSSO2 single sign-on tickets, and addresses useful for bypassing ASLR, including addresses associated with separate ABAP dialog work processes through shared memory. Stolen valid tickets can support user impersonation. Memory corruption can also crash ICM and disrupt dependent SAP services; repeated memory extraction may occur without crashing the service.
Mitigation
If you can’t patch tonight, do this now.
Until patched, disable WebSocket upgrades by setting icm/HTTP/support_websocket_upgrade=FALSE in the relevant ICM and Web Dispatcher profiles and restart those components. This disrupts WebSocket-dependent functionality. Alternatively, block WebSocket upgrades at upstream reverse proxies or web application firewalls and restrict access to vulnerable HTTP/HTTPS listeners to trusted sources. Consult SAP FAQ Note 3778788 for workaround guidance. A Web Dispatcher in front of an internal ICM is not sufficient protection by itself because it can forward malicious traffic to the backend.
Remediation
Patch, then assume compromise.
Apply the release-specific SAP kernel corrections specified in SAP Security Note 3778530, published on November 10, 2026, to every affected AS ABAP application server. Consult the note for exact vulnerable and corrected patch levels, installation prerequisites, and restart requirements; exact fixed builds are not available here. Verify the deployed kernel patch level across all instances. Separately assess and update associated SAP Web Dispatcher deployments under Security Note 3778556 for CVE-2026-89126.
Exploits
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Frequently asked questions
- Is CVE-2026-76964 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-76964 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-76964?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-76964.
- Is there a patch for CVE-2026-76964?
- Apply the release-specific SAP kernel corrections specified in SAP Security Note 3778530, published on November 10, 2026, to every affected AS ABAP application server. Consult the note for exact vulnerable and corrected patch levels, installation prerequisites, and restart requirements; exact fixed builds are not available here.
- How severe is CVE-2026-76964?
- CVE-2026-76964 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 0.43% (38th percentile) as of Nov 17, 2026.
Recent activity
60 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.