SAP ICM / Web Dispatcher · CVE-2026-76964 · CVE-2026-89126
SAP ICM2SHELL
Patch now if…If SAP's web ports are reachable. No attacks yet.
A memory bug in how SAP's built-in web server handles WebSocket traffic lets an attacker with no login leak server memory or run code as the SAP admin user (<sid>adm). It hits the ICM in NetWeaver AS ABAP and every SAP Web Dispatcher, including the one in HANA XS, and WebSocket support is on by default. SAP rates it 10.0 and fixed it on 10 Nov 2026; Onapsis ("ICM2SHELL") and nullFaktor ("SAPBleed") both built working exploits but haven't published them, and no attacks are reported.
How scary is it?
Are you affected? only if all are true
1Kernel or Web Dispatcher not patched
AS ABAP on kernel 7.40 or newer (7.22 isn't affected) and every Web Dispatcher. Fixed in 7.53 PL 1616, 7.54 PL 710, 7.77 PL 914, 7.93 PL 420 (or the updated-stack PL 401; PL 419 is still affected), 9.16 PL 111, 9.18 PL 37 and 9.20 PL 11. HANA 2.0 Web Dispatcher: 2.00.079.11 or 2.00.089.05; XS Advanced 1.0 SP05: Patch 4. Out-of-maintenance kernels (7.40, 7.41, 7.42, 7.45, 7.49, 7.73, 7.81, 7.85, 7.89) get no fix. AS Java alone isn't affected; dual-stack systems are. Check each server's kernel patch level in transaction SM51.2,5,6,8
2WebSocket upgrades are on
On by default in both the ICM and the Web Dispatcher, whether or not you use WebSockets. Not affected if icm/HTTP/support_websocket_upgrade is set to FALSE.2,3
3Attackers can reach its web port
Anyone who can reach the ICM or Web Dispatcher HTTP or HTTPS port can attack it; no SAP user or click is needed. An unpatched Web Dispatcher in front of the ICM doesn't stop the attack and can pass it on to internal systems.3,4,5
What to do
1Apply SAP Notes 3778530 and 3778556
Patch the kernel (ICM) and every Web Dispatcher, including HANA XS, to the fixed patch level for your release, then restart. On an out-of-maintenance kernel, move to a supported kernel first.1,2
Latest safe versions checked 20 Nov
2Can't patch? Turn off WebSocketcommand
Set this parameter in the ICM and Web Dispatcher profiles and restart. It breaks ABAP Push Channels and some Fiori apps, so first look for status code 101 in the ICM or Web Dispatcher HTTP log. SAP's FAQ Note 3778788 says where the parameter goes for each component.2,3
icm/HTTP/support_websocket_upgrade = FALSE3Or shield behind a patched Web Dispatcher
A Web Dispatcher on 7.53 PL 1629, 7.54 PL 723, 7.93 PL 430, 9.16 PL 200 or later protects systems behind it, but only if nothing can reach them directly (check with a network scan) and it isn't set up with PROT=ROUTER.2,8
4Keep SAP web ports off the internet
Until you've patched, limit who can reach the ICM and Web Dispatcher ports.3
This page shows you how to check. It can't tell you you're safe.
Sources (10) and changelog
- SAP: November 2026 Patch Day, Notes 3778530 and 3778556 rated 10.0 10 Nov
- Onapsis: ICM2SHELL advisory, fixed patch levels, WebSocket on by default, workarounds 12 Nov
- nullFaktor: SAPBleed write-up, memory leak, exploit withheld, workaround 12 Nov
- Full Disclosure: SAPBleed advisory, no login needed, timeline 13 Nov
- CVE record: CVE-2026-76964 (ICM), CVSS 10.0, CISA SSVC exploitation none 10 Nov
- CVE record: CVE-2026-89126 (Web Dispatcher), CVSS 10.0, CISA SSVC exploitation none 10 Nov
- CISA KEV catalog: not listed
- RedRays: check kernel level in SM51, AS Java not affected, verify shielding by scan 10 Nov
- BleepingComputer: four CVSS 10 SAP flaws, Onapsis's ICM2SHELL name 10 Nov
- SAP: researcher credits, November 2026 lists Onapsis and Raschin Tavakoli
- Published.