Skip to content
D Consultants

SAP fixes four maximum-severity flaws: what UAE businesses running SAP should do this week

SAP's November 2026 Patch Day fixed four vulnerabilities rated CVSS 10.0 in NetWeaver, Web Dispatcher and SAP Gateway. None needs a login to attack. Here is what to patch first and what to check.

Published 4 min readD Consultants team
A large structure of connected server blocks, with four beams of light sealing small gaps in its front gateway
Share this article
Summarize with AI

Key points

  1. 01SAP released its November 2026 security notes on November 10, including four flaws rated CVSS 10.0.
  2. 02The four flaws affect the ICM, Web Dispatcher, SAP Gateway and the SAML2 service provider in AS ABAP.
  3. 03None of the four requires credentials to attack, according to RedRays.
  4. 04The SAML2 flaw has no workaround, so affected systems need the patch.
  5. 05Prioritize the kernel and every Web Dispatcher, including instances outside your main landscape.

On November 10, 2026, SAP released its November security notes, including four vulnerabilities rated CVSS 10.0, the highest possible score. They affect core NetWeaver components that many SAP systems expose to networks.

What changed

SAP published 35 new security notes, four GitHub security advisories and three updates to earlier notes. The four CVSS 10.0 issues, as listed by RedRays:

  • CVE-2026-76964, ICM in AS ABAP. A WebSocket memory flaw that can be triggered before authentication.
  • CVE-2026-89126, Web Dispatcher. The same type of WebSocket flaw in the Web Dispatcher.
  • CVE-2026-89103, SAP Gateway. The default access control could treat an outside attacker as an internal application server.
  • CVE-2026-120017, SAML2 service provider in AS ABAP. In certain configurations, signatures on incoming login assertions are not checked, which can allow login as any user, including administrators.

None of the four requires credentials. Security firm Onapsis named the WebSocket pair ICM2SHELL and the Gateway flaw PROXYGATE, and reported no active exploitation of the Gateway flaw as of November 10. SAP's bulletin does not state that any of the flaws are being exploited.

Why it matters for UAE businesses

SAP runs finance, procurement, HR and supply chain for many large organizations in the region. The affected parts sit at the edge of those systems. The Web Dispatcher and ICM handle incoming web traffic. The Gateway connects SAP to other systems. SAML2 handles single sign-on.

A flaw that needs no login in one of these parts is the kind attackers move on quickly once details spread. Waiting for the next maintenance window may not be safe.

The work is not only in the main landscape. RedRays notes that 17 of the month's fixes affect the kernel, standalone Web Dispatchers or both. Teams often forget Web Dispatchers that sit in front of other systems or in separate environments.

What to do now

Treat this as an urgent change, not routine patching. We support SAP-connected platforms through Support, maintenance and migrations and build integrations through SaaS, mobile app and custom software development.

Your next steps

  1. List every exposed component

    Find every ICM, Web Dispatcher, SAP Gateway and SAML2-enabled system, across production, test and disaster recovery. Include standalone Web Dispatchers.

  2. Patch the SAML2 flaw first where you use SSO

    Check every Fiori or Web GUI system that uses SAML single sign-on. There is no workaround, so apply the note.

  3. Update kernels and Web Dispatchers

    Apply the kernel and Web Dispatcher fixes. If you cannot patch at once, SAP's workaround is to disable WebSocket support, which can break applications and integrations, so test first.

  4. Close the Gateway gap

    Apply the kernel fix, then set the profile parameter gw/acl_mode_proxy to 1. Review your secinfo and reginfo files for explicit rules.

  5. Do not forget cloud workloads

    For SAP BTP apps on Cloud Foundry, restage them once fixed buildpacks are available. Rebuild and roll out Docker and Kyma images.

Questions

Are these flaws being exploited?

SAP's bulletin does not say they are, and Onapsis reported no active exploitation of the Gateway flaw as of November 10. That can change quickly for flaws that need no login, so patch now.

Can we use a workaround instead of patching?

For the WebSocket flaws, disabling WebSocket support is possible but can break features. The SAML2 flaw has no workaround. Patching is the safe path for all four.

We use SAP through a partner. Is this still our responsibility?

Ask your partner to confirm in writing which notes are applied, on which systems and when. Responsibility depends on your contract, but the risk sits with your business.

Tags:SAPcybersecuritypatch managementERPUAE business
Share this article

Written by

D Consultants team

Software and AI team, Dubai

The people who build and run dconsults.com, our own products atnos, Vline and blaaa, and websites and AI agents for businesses across the UAE.

Profile

More articles to explore

All articles

Tell us what you are building.

Free 30-minute call. We map your workflow, find the highest-impact opportunity and send a clear proposal.

+971 50 807 0826