SAP releases fixes for four maximum-severity NetWeaver flaws

SAP has released fixes for four vulnerabilities rated CVSS 10.0 in its November Security Patch Day, including two flaws that can enable remote code execution without authentication. Three issues affect SAP NetWeaver Application Server ABAP components, while one affects SAP Web Dispatcher, which receives web requests and forwards them to application servers.
The issues are CVE-2026-76964 in Internet Communication Manager (ICM), CVE-2026-89126 in SAP Web Dispatcher, CVE-2026-89103 in SAP Gateway, and CVE-2026-120017 in the SAML 2.0 service provider for NetWeaver AS ABAP and ABAP Platform. SAP advises customers to apply the relevant corrections as a priority.
Two network-reachable paths to code execution
CVE-2026-76964 and CVE-2026-89126 involve malformed WebSocket control frames with invalid length fields. In the affected ICM and Web Dispatcher components, crafted network traffic can trigger memory corruption before a user logs in. A successful attacker could run code and fully compromise the affected system.
The ICM issue affects NetWeaver AS ABAP, not NetWeaver AS Java. Its correction is delivered through dw.sar and the SP Stack Kernel. RedRays notes that a patched Web Dispatcher can shield an ICM reachable only through that component, but only when the ICM ports have no direct exposure. Disabling WebSocket support is a last-resort mitigation because it can interrupt dependent functions.
The Web Dispatcher flaw has the same underlying cause and affects both standalone and embedded deployments, including instances in SAP HANA XS Classic and XS Advanced. SAP Content Server is not affected. RedRays advises organisations to locate every Web Dispatcher, since an overlooked instance remains exposed. Available update paths include SAPWEBDISP.SAR for standalone deployments and dw.sar or the SP Stack Kernel for embedded instances.
Authentication and gateway trust risks
CVE-2026-120017 affects SAML configurations in which the service provider did not validate signatures on incoming assertions. Under those conditions, an attacker could sign in as any user, including privileged users. SAP says a complete compromise could follow and may extend to connected systems. There is no workaround; the correction instructions or listed support package are the available remedy.
Systems using SAML2 for browser logon, including Fiori Launchpad or Web GUI behind an identity provider, should be treated as in scope until configuration and patch status are confirmed. RedRays also recommends reviewing trusted identity providers in transaction SAML2 and checking audit logs for privileged SAML logons from unexpected sources.
CVE-2026-89103 concerns SAP Gateway access-control behaviour. Where secinfo and reginfo contain no explicit rules, or rely on the internal host keyword, the gateway can fall back to rules allowing the system's own application servers. An external attacker able to present as one of those servers could take unauthorised actions in the application environment.
Patch scope and operational priorities
SAP issued separate notes for each vulnerability: Note 3778530 for ICM, Note 3778556 for Web Dispatcher, Note 3798345 for SAP Gateway, and Note 3849308 for the SAML2 service provider. Affected releases span multiple kernel, Web Dispatcher and SAP_BASIS versions, so administrators need to match each installed component to its applicable note.
RedRays recommends updating the kernel and all Web Dispatchers in one rollout to levels covering all 17 kernel and Web Dispatcher fixes released this month. For Gateway, it advises applying the fix, setting gw/acl_mode_proxy where applicable, confirming gw/acl_mode is 1, defining explicit secinfo and reginfo rules, and preventing access to gateway port 33xx from user networks or the internet. The practical business implication is to combine urgent patch deployment with an exposure review, because these flaws require no user action and affect identity, web-facing and internal trust paths at once.

