IPCRIME | VULNERABILITY WATCH | 15 NOVEMBER 2026
SAP’s November 10 security update included four vulnerabilities assessed at the maximum CVSS 10.0 severity, covering application-server traffic handling, Web Dispatcher, SAP Gateway and single sign-on. Administrators preparing their next maintenance window should review affected components and release-specific fixes rather than assuming a generic patch addresses every deployment.
The four reported issues
The vulnerabilities are CVE-2026-76964 in NetWeaver’s Internet Communication Manager, CVE-2026-89126 in SAP Web Dispatcher, CVE-2026-89103 in SAP Gateway and CVE-2026-120017 in the SAML2 service-provider component. The ICM and Web Dispatcher problems may enable code execution from crafted network traffic in vulnerable deployments, while the other two concern trust and authentication behavior.
Exposure depends on configuration
Affected products and version ranges differ. The SAML issue is relevant to specific SAML-based sign-in configurations, and the Gateway issue is affected by access-control configuration. Research published alongside SAP’s notes warns that a patched component with permissive gateway proxy rules may still leave unnecessary access open. Review the vendor notes for the precise kernel or support-package requirements.
Do not confuse severity with exploitation
A maximum severity rating signals a potentially severe outcome under the relevant conditions; it is not evidence that attackers are already exploiting all four flaws. The published analysis cited here said researchers had not observed exploitation of the disclosed ICM, Web Dispatcher and Gateway issues when that analysis was released.
Immediate next steps
Identify each NetWeaver instance, every Web Dispatcher and Gateway, verify maintenance status and isolate exposed administrative or internal service ports. Coordinate updates with SAP administrators and test business-critical integrations after patching.
Source documents and further reading
Independent IPCRIME research-based coverage. Incident dates, agency publication dates and the date of this article are distinguished above. Product guidance is not a claim of independent penetration testing.