Symptom
An administrator is logged on to the administration UI of SAP Web Dispatcher or of the Internet Communication Manager (ICM) and opens a link from an email, a chat or a web page. In the background, the link sends a request to the administration UI, and the server carries it out with the administrator's privileges. No password prompt and no error message appear.
SAP rates the impact as follows:
- SAP Web Dispatcher and ICM of SAP NetWeaver AS ABAP (CVE-2026-89119): CVSS 9.6. A successful attack can lead to a full compromise of the underlying operating system.
- SAP Web Dispatcher of SAP HANA XSA (CVE-2026-120014): CVSS 7.6. A successful attack can temporarily compromise the Web Dispatcher, with high impact on confidentiality.
The attack usually goes unnoticed, because every request carries the administrator's valid session. In the logs it looks like a normal administrative action. The typical trigger is a phishing link that an administrator opens while the administration UI is still open in another browser tab.
Cause
The administration UI does not check thoroughly enough whether a request really comes from the UI itself. The browser therefore attaches the administrator's session to requests that another website started, a pattern known as cross-site request forgery (CSRF). The attacker does not need an account on the system.
Who is affected
All of the following must apply:
- The system runs one of these components below the patch level that contains the correction:
- SAP Web Dispatcher or SAP kernel 7.93 below patch level 424
- SAP Web Dispatcher or SAP kernel 9.16 below patch level 119
- SAP kernel 9.20 below patch level 19
- SAP kernel 9.21 below patch level 7
- SAP HANA XSA below version 1.5.5
- The Web Dispatcher or ICM administration UI (
/sap/adminor/sap/wdisp/admin) is enabled with aicm/HTTP/admin_<x>parameter. - At least one user of the administration UI has the
adminrole.
Not affected: SAP NetWeaver AS Java, and the Web Dispatcher that is part of SAP HANA XSC.
To check the patch level and whether the administration UI is enabled, run the following as <sid>adm:
# Standalone SAP Web Dispatcher
sapwebdisp -v | grep -iE "kernel release|patch number"
# ICM and embedded Web Dispatcher of AS ABAP
disp+work -v | grep -iE "kernel release|patch number"
# Administration UI parameters in all profiles
grep -E "^[[:space:]]*icm/HTTP/admin_" /usr/sap/<SID>/SYS/profile/*In AS ABAP you can also check the kernel patch level in transaction SM51 (Release Info) and the parameter in transaction RZ11.
Read the result as follows: you are affected if the patch number is lower than the fixed patch level for your kernel release and at least one icm/HTTP/admin_<x> parameter has a value. Then check the user administration of the administration UI, or the authentication file referenced by icm/HTTP/auth_<x> (often icmauth.txt), for users with the admin role. If no user has that role, the system is not affected.
Prevent the issue on SAP Web Dispatcher, ICM and XSA
At the time of writing, SAP delivers the correction with the patch levels listed above and all later ones. Only the latest kernel patch is available for download, and it contains all earlier corrections.
- Standalone SAP Web Dispatcher: install the latest
SAPWEBDISP.SAR. - ICM and embedded Web Dispatcher: apply the latest SP Stack Kernel (
SAPEXE.SARandSAPEXEDB.SAR) if its patch level is equal to or higher than the fixed level. If it is not, the next SP Stack Kernel will contain the correction. Install the hotfixdw.saronly if you cannot wait for it. - Kernel releases out of maintenance: the correction may not be available. Upgrade to the corresponding downward-compatible kernel.
- SAP HANA XSA: update XSA to version 1.5.5 or higher.
Before you install a kernel patch, check what SAP reports about known regressions for the target patch level.
If you cannot patch right away, disable the administration UI as a temporary workaround. Set icm/HTTP/admin_0 to an empty value in the instance or Web Dispatcher profile, and comment out all other icm/HTTP/admin_<x> parameters in the default and instance profiles:
icm/HTTP/admin_0 =
# icm/HTTP/admin_1 = <ORIGINAL_VALUE>Then restart the Web Dispatcher or all application servers.
Alternatively, remove the admin role from all users of the administration UI and assign the monitor role instead.
Keep in mind:
- The workaround is temporary. SAP strongly recommends installing the correction, either instead of the workaround or after it.
- Without the administration UI, you change Web Dispatcher and ICM settings only through profiles and command-line tools. With the
monitorrole, the UI stays available for read-only monitoring. - Restarting application servers interrupts user sessions. Plan a maintenance window, or restart the servers one after the other if your landscape allows it.
- To undo the workaround after patching, restore the original
icm/HTTP/admin_<x>values or theadminrole assignments, and restart again.
On premise, you patch the kernel and XSA yourself. If SAP operates your systems, for example SAP S/4HANA Cloud Private Edition, check the patch schedule with SAP's cloud operations team instead of changing profiles yourself.
Confirm the result
After patching, run sapwebdisp -v or disp+work -v again on every instance and confirm that the patch number is at or above the fixed level. Remember that each standalone Web Dispatcher, including those in front of non-production systems, needs its own patch.
If you applied the workaround, confirm that /sap/admin and /sap/wdisp/admin no longer respond, or that no user has the admin role anymore.
Then review the HTTP access logs and the profile change history for administrative actions that nobody on your team carried out, especially changes to profiles, routing rules or users. If you find any, treat it as a security incident and contact SAP Support.