On this page (7 sections)

SAP Web Dispatcher and the Internet Communication Manager (ICM) in SAP NetWeaver Application Server ABAP do not sufficiently validate requests in certain administrative functionality. The flaw is tracked as CVE-2026-89119 and was published on 2026-11-10 with a critical CVSS score of 9.6, according to the NVD record.

If you run SAP landscapes, or host or manage them for others, this one deserves attention. It requires a logged-on administrator to be tricked, so the risk sits in how and where administrators browse as much as in the software itself.

What happened

According to the NVD entry, certain administrative functions in SAP Web Dispatcher and in the ICM of SAP NetWeaver AS ABAP do not perform sufficient request validation. An unauthenticated attacker could trick a logged-on administrator into visiting a malicious link, which could cause unintended actions in that administrator's session.

The record states that successful exploitation could lead to full compromise of the underlying operating system, with high impact on confidentiality, integrity and availability. SAP references the issue in SAP Note 3804858 and on its security patch day page.

Only one independent publisher (the NVD record) covers this story so far. The research does not include a vendor advisory text, affected version ranges or fixed versions. Read SAP Note 3804858 directly, which typically requires an SAP account, before planning your update.

The weakness in plain terms

CWE-352 is cross-site request forgery (CSRF). Web applications often trust any request that arrives with a valid session cookie. If the application does not also check that the request was deliberately made by the user, for example with an anti-forgery token, a hostile web page or link can make the administrator's browser send a request on their behalf.

The attacker never needs the administrator's password. They need the administrator to be signed in to the administrative interface and to open a crafted link. The impact then depends on what that administrative function can do, and here the record describes a path to operating system compromise.

Who is realistically exposed

  • Organizations running SAP Web Dispatcher as a reverse proxy or load balancer in front of SAP systems.
  • Organizations running SAP NetWeaver Application Server ABAP, which includes the ICM component.
  • Teams where administrators use the same browser for SAP administration and for general web browsing or email.
  • Hosting providers and consultancies that administer SAP systems for customers.

The research does not say whether the vulnerable administrative functions are reachable from the internet or only from internal networks, and it does not give affected version ranges. Treat every Web Dispatcher and ABAP server as potentially in scope until SAP's note tells you otherwise.

How to check your exposure

  1. Inventory every SAP Web Dispatcher instance and every NetWeaver AS ABAP system that uses the ICM, including development and test systems.
  2. Open SAP Note 3804858 and compare the affected and fixed releases it lists with the kernel and component versions you run.
  3. Identify who has administrative access to the Web Dispatcher and ICM administration interfaces, and from which networks and browsers they use it.
  4. Check whether those administrative interfaces are reachable from outside your trusted network.

What to do now

  1. Read SAP Note 3804858 and the SAP security patch day page, and note the fixed versions for your releases.
  2. Schedule and apply the SAP-provided correction to every affected Web Dispatcher and ABAP system, starting with internet-facing ones.
  3. Until patched, restrict access to administrative functionality to trusted management networks only.
  4. Ask administrators to avoid browsing the web or opening unknown links while signed in to SAP administrative interfaces, and to sign out when finished.
  5. Use a dedicated browser profile or workstation for SAP administration.
  6. Review administrative activity logs for unexpected configuration changes since your last known good state.
  7. If you find signs of unexpected administrative actions, treat the host as potentially compromised and follow your incident response process.
Caution. Patching SAP kernel and server components usually means restarting services. Plan the change window, test in a non-production system first and take backups before you apply it.

Detection and monitoring afterwards

The research gives no indicators of compromise and no reports of exploitation, so there is nothing specific to hunt for beyond general good practice. Watch administrative audit logs for configuration changes that nobody on your team made, and for administrative requests that coincide with an administrator visiting external sites.

Because a CSRF attack rides on a legitimate session, the requests can look normal in access logs. Referrer and origin patterns, odd timing, and changes you cannot tie to a change ticket are the most useful signals. A web application firewall in front of administrative paths can add another layer, as described in our guide on what a WAF is, but it is not a substitute for applying SAP's correction.

For the public-facing side of your estate, uptime, certificate and DNS monitoring can help you notice unexpected changes, though it does not replace SAP's own administrative audit logs.

Timeline

Known dates from the research
DateEvent
2026-11-10CVE-2026-89119 published in the NVD with a CVSS score of 9.6

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-89119: SAP Web Dispatcher and SAP NetWeaver Application Server ABAP (Internet Communication Manager) do not perform sufficient request validation in certain…nvd.nist.gov ·
  • SAP
  • CSRF
  • CVE-2026-89119
  • Web Dispatcher
  • NetWeaver