SAP released its SAP November 2026 security patches on November 10, 2026, addressing 35 vulnerabilities across its product portfolio. Four of those flaws carry the maximum CVSS 10.0 rating and affect core infrastructure components that handle web traffic, authentication, and gateway communications. The updates are available now through the SAP Support Portal.
What happened
On its November 2026 Security Patch Day, SAP published 35 new security notes and four GitHub security advisories, plus updates to three previously released notes. The most severe issues are four critical vulnerabilities rated CVSS 10.0, all exploitable by unauthenticated attackers over the network with no user interaction required.
| CVE | Component | Flaw Type | Tracking Name |
|---|---|---|---|
| CVE-2026-76964 | NetWeaver AS ABAP (Internet Communication Manager) | Memory Corruption | ICM2SHELL |
| CVE-2026-89126 | SAP Web Dispatcher | Memory Corruption | ICM2SHELL |
| CVE-2026-89103 | SAP Gateway | Broken Access Control | PROXYGATE |
| CVE-2026-120017 | NetWeaver AS ABAP / ABAP Platform (SAML2 Service Provider) | Missing Authentication | — |
The two memory corruption flaws (CVE-2026-76964 and CVE-2026-89126) are collectively tracked as ICM2SHELL by Onapsis, the research firm that discovered them. They reside in the WebSocket handling code of the Internet Communication Manager (ICM) and the Web Dispatcher reverse proxy. The Gateway flaw (CVE-2026-89103), dubbed PROXYGATE, stems from a default access control list that treats external callers as trusted internal application servers. The SAML2 flaw (CVE-2026-120017) allows authentication bypass when certain configurations skip signature verification on incoming assertions.
Why it matters
NetWeaver is the core application platform underpinning SAP's business software suite. It handles application integration, authentication, user management, and data processing. The Web Dispatcher acts as a reverse proxy and load balancer for SAP systems, while SAP Gateway exposes OData services for frontend applications. The SAML2 Service Provider manages single sign-on for enterprise users.
Because these components sit at the network edge, they are frequently exposed to the internet or to large internal networks. An unauthenticated attacker who can reach any of these services could achieve remote code execution as the SAP installation owner (<sid>adm), effectively taking full control of the affected system.
The Singapore Cyber Security Agency (CSA) issued an alert on November 16, 2026, urging immediate patching. Beazley Security and Zscaler also published advisories emphasizing that exposure depends on network reachability and configuration, but that the severity score alone should drive urgent action.
SAP November 2026 security patches: what you should do
-
Apply the relevant SAP Security Notes immediately. SAP strongly recommends visiting the Support Portal and applying patches on priority. The key notes for the four critical flaws are:
- Note 3778530 for CVE-2026-76964 (ICM)
- Note 3778556 for CVE-2026-89126 (Web Dispatcher)
- Note 3798345 for CVE-2026-89103 (Gateway)
- Note 3849308 for CVE-2026-120017 (SAML2)
-
Check every Gateway, ICM, and Web Dispatcher instance in your landscape. The November 2026 patch day overview lists all 35 new notes; review it for other critical and high-severity issues affecting components you use.
-
Apply post-patch configuration for PROXYGATE. After implementing Note 3798345, you must manually set a profile parameter to secure the Gateway. The patch alone does not fully mitigate CVE-2026-89103.
-
If immediate patching is not possible, implement interim mitigations:
- Restrict network access to ICM, Web Dispatcher, and Gateway services to trusted IP ranges only.
- For ICM2SHELL: Route ICM traffic through a patched Web Dispatcher and keep ICM ports unreachable from untrusted networks. Disabling WebSocket support in the Web Dispatcher is a workaround but breaks ABAP Push Channels and some Fiori features.
- Review SAML2 configurations and
prxyinfo/gw/acl_mode_proxysettings for PROXYGATE exposure.
-
Verify kernel patch levels. Fixed kernel versions vary by release. For example, KERNEL 7.53 requires PL 1616/1617; 7.54 requires PL 710; 7.77 requires PL 914; 7.93 requires PL 401. Confirm the exact patch level for your installation in the security note details.
-
Monitor for exploitation signals. While no in-the-wild exploitation was reported at release, these vulnerabilities are high-value targets. Review logs for anomalous WebSocket traffic, unexpected Gateway requests, or SAML authentication anomalies.
The bottom line
SAP's November 2026 security patches close 35 vulnerabilities, including four maximum-severity flaws that allow unauthenticated remote code execution in widely deployed edge components. The affected components—ICM, Web Dispatcher, Gateway, and SAML2—are central to SAP system connectivity and authentication. Apply the security notes now, implement the required Gateway configuration change, and restrict network exposure where patching will take time.
Sources
- SAP Patches 35 Vulnerabilities, Including Four Critical Flaws in NetWeaver, Web Dispatcher, and Gateway
- SAP Security Patch Day - November 2026
- SAP patches ICM2SHELL and PROXYGATE maximum severity flaws
- Multiple Vulnerabilities in SAP Products (CSA Singapore)
- Critical Vulnerabilities in SAP NetWeaver, Web Dispatcher and Gateway (Beazley Security)
- SAP November 2026 Patch Day: Four CVSS 10.0 Flaws Explained (Zscaler)
- SAP Security Notes: November 2026 Patch Day (Onapsis)