Skip to main content
Mallory
CriticalVulnerability

CVE-2026-89126: ICM2SHELL in SAP Web Dispatcher

Published Nov 10, 2026 · Updated today
Trending this week#77of 427,955 vulnerabilities
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v3.1
EPSS0.43%38th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-89126CWE-122 · Heap-based Buffer Overflow

CVE-2026-89126 is a heap-based buffer overflow in SAP Web Dispatcher, collectively named ICM2SHELL with CVE-2026-76964. Insufficient validation of WebSocket control-frame lengths allows specially crafted network traffic to corrupt heap memory, potentially enabling unauthenticated remote code execution or service termination. The vulnerability affects standalone and embedded Web Dispatchers, including those used by SAP HANA XS Classic and XS Advanced. The specific vulnerable function is not publicly identified.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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 compromise the affected SAP system's confidentiality, integrity, and availability through arbitrary code execution, unauthorized access to business data and stored credentials, modification of application settings, or service disruption. Code executes with the operating-system privileges of the Web Dispatcher process, commonly the SAP installation owner account; exploitation does not automatically grant root privileges. Memory corruption can also crash the dispatcher and interrupt access to backend applications.

Mitigation

If you can’t patch tonight, do this now.

Until patching is complete, restrict network access to affected HTTP and HTTPS listeners to necessary trusted clients or intermediaries. Where operationally feasible, block WebSocket upgrades at an upstream reverse proxy or web application firewall, or disable WebSocket support; these measures can disrupt dependent applications. Network restrictions must protect the vulnerable dispatcher itself, and neither ordinary HTTP filtering nor placement in a DMZ substitutes for patching.

Remediation

Patch, then assume compromise.

Apply the corrected Web Dispatcher binaries or applicable SAP kernel or HANA component updates specified in SAP Security Note 3778556, released November 10, 2026. Consult accompanying FAQ Note 3778788 and confirm the exact affected releases and corrected patch levels for each installation. Include standalone and embedded instances, prioritize internet-facing deployments, restart updated instances as required, and verify their running patch levels. Exact corrected build numbers are not available here.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2026-89126 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-89126 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-89126?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-89126.
Is there a patch for CVE-2026-89126?
Apply the corrected Web Dispatcher binaries or applicable SAP kernel or HANA component updates specified in SAP Security Note 3778556, released November 10, 2026. Consult accompanying FAQ Note 3778788 and confirm the exact affected releases and corrected patch levels for each installation.
How severe is CVE-2026-89126?
CVE-2026-89126 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 0.43% (38th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

56 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.