SAP OVERPASS and S4GET Vulnerabilities Expose ERP Kernels

SAP released security patches addressing OVERPASS (CVE-2026-44756) and S4GET (CVE-2026-58240), two unauthenticated flaws allowing remote command execution on host systems running SAP kernels.

TL;DR

  • On 8 September 2026, SAP released Security Notes for two critical vulnerabilities: CVE-2026-44756 (OVERPASS, CVSS 10.0) and CVE-2026-58240 (S4GET, CVSS 9.8).
  • CVE-2026-44756 stems from missing boundary validation during Extended Passport (EPP) deserialisation in the SAP Kernel, enabling unauthenticated remote operating system command execution under SAP administrative privileges.
  • CVE-2026-58240 allows unauthenticated attackers to register malicious components directly with the SAP NetWeaver Message Server, abusing missing component authentication to achieve cluster-wide trust propagation and remote OS execution.
  • Standard network firewalls cannot mitigate S4GET without disrupting legitimate SAP GUI end-user logon, rendering host-level kernel patching mandatory.
  • Immediate remediation requires applying SAP Security Note 3747649 (OVERPASS) and SAP Security Note 3759472 (S4GET) across affected SAP Kernel binaries (versions 7.22 to 9.20) and SAP Web Dispatcher.

On 8 September 2026, SAP published its monthly patch bundle, highlighting two maximum-severity vulnerabilities that strike at the foundational kernel and cluster orchestration layers of SAP NetWeaver. The most critical flaw, tracked as sap overpass cve-2026-44756 with a CVSS score of 10.0, affects the SAP Kernel library responsible for parsing trace and telemetry header structures. Running alongside it is CVE-2026-58240 (nicknamed S4GET), a CVSS 9.8 vulnerability inside the SAP NetWeaver Message Server. Both vulnerabilities were discovered and responsibly disclosed by Onapsis Research Labs.

These security flaws represent a severe threat to enterprise resource planning (ERP) systems. Both issues allow unauthenticated attackers to execute arbitrary operating system commands with full SAP administrative privileges over a network connection. Because SAP application servers run under privileged system accounts—typically <sid>adm—successful exploitation exposes core business data, database credentials, and operational logic to complete compromise.

For systems architects and security operations engineering teams, these vulnerabilities challenge standard assumptions regarding perimeter-based network defense. While OVERPASS affects both edge proxies and backend kernels, S4GET directly exploits the port used by SAP GUI clients. This architectural dependency means blocking the vulnerability at the firewall level breaks legitimate user access, leaving kernel-level binary updates as the sole viable path to remediation.

Critical Flaws in Core SAP Infrastructure Components

The SAP September 2026 Security Patch Day addressed vulnerabilities that impact the binary infrastructure underlying nearly all NetWeaver-based installations, including S/4HANA systems. Rather than residing in higher-level ABAP business code or Java applications, these flaws exist in the C/C++ compiled kernel libraries and central cluster daemons. As documented by CERT-EU Advisory 2026-011, the vulnerabilities affect a wide span of active kernel release cycles.

The first flaw, CVE-2026-44756 (OVERPASS), carries the maximum possible CVSS score of 10.0. It resides in the SAP Kernel library that processes Extended Passport (EPP) structure formats. Extended Passports are distributed tracing payloads appended to internal and external communications across SAP systems. Because the parser lacks boundary checks during data deserialisation, an unauthenticated attacker can submit a single crafted network request containing a malformed EPP header to trigger memory corruption and achieve arbitrary OS command execution.

The second flaw, CVE-2026-58240 (S4GET), carries a CVSS score of 9.8 and targets component BC-CST-MS within the SAP NetWeaver Message Server. The Message Server serves as the central directory and load-balancing engine for SAP application server instances. Due to a missing authentication check during internal application server component registration, an unauthenticated remote attacker can connect to the Message Server port, register a rogue application component, and elevate that component to a trusted node within the cluster. Once trusted, the attacker can leverage internal cluster communications to execute commands on the host machine as the operating system user running SAP.

As of publication, public sources have not disclosed whether active exploitation in the wild occurred prior to SAP’s patch release. Additionally, public proof-of-concept exploit code outside Onapsis Research Labs disclosures remains unconfirmed. However, given that both flaws grant complete operating system control without authentication, security teams must treat all unpatched SAP kernels as critically exposed.

Anatomy of CVE-2026-44756: Extended Passport Memory Corruption

To understand CVE-2026-44756, engineering teams must examine how SAP handles distributed tracking context. The Extended Passport (EPP) is a proprietary header structure introduced by SAP to trace transactions across complex, multi-tiered landscapes. When an action originates—whether through SAP Web Dispatcher, an Internet Communication Manager (ICM) HTTP request, or an RFC function call—the system generates an EPP payload. This payload carries metadata including transaction GUIDs, root context IDs, connection counters, and client network identifiers.

When an SAP application server or gateway service receives an incoming request containing an EPP payload, it passes the data stream to internal C/C++ kernel functions for parsing and deserialisation. Deserialisation converts the serialized wire data back into memory structures allocated within the process space. In affected SAP Kernel versions, the deserialisation routine fails to perform strict length checking and memory boundary validation on dynamic EPP fields.

+-----------------------------------------------------------------------+
|                         Malformed Network Packet                      |
|  [ HTTP / RFC / DIAG Protocol Envelope ]                              |
|  +-----------------------------------------------------------------+  |
|  |  Malformed EPP Header (Unvalidated Length Fields / Payload)     |  |
|  +-----------------------------------------------------------------+  |
+-----------------------------------+-----------------------------------+
                                    |
                                    v
+-----------------------------------------------------------------------+
|                      SAP Kernel Processing Layer                      |
|  [ disp+work / icmbnd / sapwebdisp ]                                 |
|                                                                       |
|  1. Ingress parser reads EPP header length                            |
|  2. Deserialisation logic allocates memory buffer                     |
|  3. Missing Boundary Check: Data payload exceeds buffer bounds        |
|  4. Heap/Stack Memory Corruption                                      |
+-----------------------------------+-----------------------------------+
                                    |
                                    v
+-----------------------------------------------------------------------+
|                    Execution Flow Hijack / Exploitation               |
|                                                                       |
|  - Process context overwritten (pointers / instruction offsets)       |
|  - Abrupt termination or execution of injected payload                |
|  - Arbitrary OS Command Execution under <sid>adm credentials           |
+-----------------------------------------------------------------------+

An attacker can construct a network packet with intentionally mismatched field lengths or over-sized telemetry attributes inside the EPP header. When the kernel process attempts to reconstruct the EPP data in memory, the lack of boundary bounds checking leads to memory corruption. While SAP’s CVE entry notes that this can cause undefined behaviour and abnormal program termination, security research confirms that carefully controlled memory corruption allows an attacker to hijack process execution flow. Because kernel components like disp+work or sapwebdisp execute directly under the SAP installation owner (e.g., sidadm), the hijacked thread grants immediate operating system command execution at that privilege level.

While vendor advisories confirm that missing deserialisation boundaries cause the failure, exact binary-level patch diffing details for the kernel libraries have not been publicly disclosed. Systems engineers can verify whether their deployed kernel is vulnerable by cross-referencing compiled patch levels using the disp+work -v tool against the fix matrices in SAP Security Note 3747649.

Anatomy of CVE-2026-58240: Cluster Trust Exploitation in Message Server

While OVERPASS targets memory management flaws in network parsers, CVE-2026-58240 (S4GET) exploits a logical flaw in SAP’s cluster membership model. The SAP NetWeaver Message Server (component BC-CST-MS) acts as the central coordinator for an SAP system. It maintains the master list of all active Primary Application Servers (PAS), Additional Application Servers (AAS), and background instances composing the system cluster.

When an SAP application server starts, it initiates an internal registration handshake with the central Message Server. This process registers the server’s instance name, IP address, dispatched services, and capacity weights. However, the Message Server software handling component registration in component BC-CST-MS fails to require or validate authentication credentials during this initial handshake.

+-------------------+         Unauthenticated Component          +--------------------+
|  Attacker Client  | ------ Registration Request ------------> | SAP Message Server |
|  (Rogue Node)     |        (No credentials checked)           | (component         |
+-------------------+                                           |  BC-CST-MS)        |
                                                                +---------+----------+
                                                                          |
                                                                          | Registers node &
                                                                          | propagates trust
                                                                          v
+------------------------------------------------------------------------------------+
|                             SAP NetWeaver Cluster Zone                             |
|                                                                                    |
|   +--------------------------+                      +--------------------------+   |
|   | Application Server PAS 01 | <--- Node Sync ----> | Application Server AAS 02 |   |
|   | Trusting All MS Nodes    |                      | Trusting All MS Nodes    |   |
|   +--------------------------+                      +--------------------------+   |
+------------------------------------------------------------------------------------+
                                          |
                                          v
+------------------------------------------------------------------------------------+
| Remote Command Execution: Attacker dispatches internal cluster commands to any      |
| application server, executing OS commands under the <sid>adm operating system account.|
+------------------------------------------------------------------------------------+

An attacker connected to the Message Server service port can send a malformed registration payload claiming to be a newly initialized internal application instance. Because no authentication challenge occurs, the Message Server accepts the registration request, adds the rogue instance to the internal cluster table, and promotes the attacker-controlled endpoint to a trusted cluster node.

The architectural danger of S4GET lies in trust propagation. The Message Server automatically propagates the presence and trusted status of the newly registered node to all legitimate application servers connected across the landscape. The existing application servers accept the Message Server’s updated topology state without independent verification. Once established as a trusted node, the attacker can submit cluster management calls, trigger task execution routines, or inject control parameters that result in remote command execution across any or all hosts in the SAP system under the <sid>adm account context.

Systemic Blast Radius Across Kernel and Web Dispatcher Versions

The operational impact of OVERPASS and S4GET is magnified by the broad distribution of vulnerable kernel releases. Because SAP Kernel code is shared across multiple product releases—including SAP S/4HANA, SAP Business Suite (ECC), NetWeaver Application Server ABAP, and NetWeaver Application Server Java—a vulnerability in the kernel library affects almost all deployed instances running on those versions.

System-Wide Exposure Context

Both vulnerabilities execute within the operating system user context that runs the SAP instance (typically <sid>adm). Compromise of this account provides full control over SAP database connection secrets, local file systems, system binaries, and the ability to read or tamper with underlying business data.

The following matrix outlines the specific software components and release ranges affected by each vulnerability, as published in SAP Security Notes 3747649 and 3759472:

Vulnerability / CVE Affected Component Vulnerable Software Releases SAP Security Note
CVE-2026-44756 (OVERPASS) KRNL64NUC 7.22, 7.22EXT 3747649
CVE-2026-44756 (OVERPASS) KRNL64UC 7.22, 7.22EXT, 7.53, 8.04 3747649
CVE-2026-44756 (OVERPASS) KERNEL 7.22, 7.53, 7.54, 7.77, 7.89, 7.93, 8.04, 9.16, 9.18, 9.19, 9.20 3747649
CVE-2026-44756 (OVERPASS) WEBDISP 9.16, 9.18, 9.19, 9.20 3747649
CVE-2026-58240 (S4GET) KERNEL (BC-CST-MS) 9.16, 9.18, 9.19, 9.20 3759472

The inclusion of SAP Web Dispatcher (WEBDISP) in the vulnerability scope for CVE-2026-44756 increases the perimeter risk. Web Dispatcher instances deployed in demilitarised zones (DMZs) to handle external reverse proxy routing and load balancing expose the unvalidated EPP deserialisation path directly to untrusted ingress networks. An attacker reaching an edge Web Dispatcher can compromise the DMZ host without needing network visibility into the internal database or backend network segments.

Network Accessibility and Perimeter Mitigation Challenges

Enterprise network security teams frequently attempt to mitigate infrastructure vulnerabilities by deploying edge firewalls, web application firewalls (WAFs), or access control lists (ACLs). However, the architectural design of SAP NetWeaver cluster communication renders perimeter firewalls ineffective against CVE-2026-58240 (S4GET).

The SAP NetWeaver Message Server listens on a dedicated public network port—by default, 36<sysnr> for text-based client communication and 39<sysnr> for internal SAP protocol traffic (where <sysnr> represents the two-digit SAP system number). Legitimate end-user client software, including SAP GUI for Windows and SAP GUI for Java, requires direct network access to port 36<sysnr> during initial session startup. The Message Server queries current instance workloads and returns the IP address and port of the optimal application server to the SAP GUI client.

Firewall Mitigation Trade-off

Blocking incoming traffic to Message Server port 36<sysnr> at a network boundary prevents external exploitation of S4GET. However, doing so immediately breaks user authentication and dynamic load balancing for all remote SAP GUI sessions across the enterprise.

Furthermore, WAF devices positioned at the HTTP/HTTPS boundary fail to mitigate raw binary protocols or proprietary DIAG/RFC protocol streams that wrap EPP payloads targeted by CVE-2026-44756. Deep Packet Inspection (DPI) engines typically lack structural schemas for parsing internal SAP binary headers. Consequently, relying on perimeter defenses without applying the vendor kernel patch leaves systems completely exposed to internal lateral movement or compromised VPN endpoints.

Step-by-Step Remediation and Patch Deployment Plan

Remediating OVERPASS and S4GET requires replacing active kernel binary sets across all SAP Web Dispatchers, Central Services instances (ASCS/SCS), Primary Application Servers (PAS), and Additional Application Servers (AAS). Because kernel updates require process restarts, Basis teams must execute updates in a coordinated sequence to minimize business disruption.

Step 1: Download and Verify Security Notes

Log into the SAP Support Portal and retrieve the patch files specified in SAP Security Note 3747649 (for CVE-2026-44756) and SAP Security Note 3759472 (for CVE-2026-58240). Verify the cryptographic checksums (SHA-256) of the downloaded SAR archive files (e.g., SAPEXE.SAR, SAPEXEDB.SAR, WDISP.SAR) before staging them on target operating systems.

Step 2: Staging and Patching SAP Web Dispatcher

Patch external-facing SAP Web Dispatchers first to mitigate perimeter exposure to OVERPASS. Extract the new binary payload using SAPCAR while the service remains online, then perform a rolling service restart.

# Log in as the web dispatcher operating system user (e.g., wd1adm)
cd /usr/sap/WD1/exe

# Extract updated binary archive into a temporary directory
/usr/sap/WD1/exe/SAPCAR -xvf /tmp/patches/WDISP_PATCH.SAR -R /tmp/new_exe/

# Check updated binary build version test in staging
/tmp/new_exe/sapwebdisp -v

# Stop Web Dispatcher instance safely
sapcontrol -nr 00 -function Stop

# Overwrite active binaries with patched executables
cp -r /tmp/new_exe/* /usr/sap/WD1/exe/

# Restart Web Dispatcher instance
sapcontrol -nr 00 -function Start

Step 3: Patching Central Services (ASCS/SCS) and Message Server

Next, update the Central Services instance hosting the SAP NetWeaver Message Server to address CVE-2026-58240. Schedule a system maintenance window, as restarting Central Services affects application server node connectivity.

# Log in as the SAP System Administrator account
su - prdadm

# Check active kernel patch version before update
disp+work -v

# Stop Application Server instances and Central Services
sapcontrol -nr 01 -function StopSystem ALL

# Extract updated SAPEXE.SAR and SAPEXEDB.SAR archives to central directory
SAPCAR -xvf /tmp/patches/SAPEXE.SAR -R /usr/sap/PRD/SYS/exe/uc/linuxx86_64/
SAPCAR -xvf /tmp/patches/SAPEXEDB.SAR -R /usr/sap/PRD/SYS/exe/uc/linuxx86_64/

# Restart SAP Central Services and Message Server
sapcontrol -nr 00 -function StartInstance

# Restart remaining Application Servers
sapcontrol -nr 01 -function StartSystem ALL

Post-Patch Verification and Host Infrastructure Hardening

Once kernel updates are deployed, systems engineers must verify patch installation and implement defense-in-depth measures at the host level.

1. Kernel Version Verification

Execute binary version verification commands across all SAP instances to ensure old kernel executables are not retained in executable search paths or local instance directories.

# Verify disp+work binary build level
/usr/sap/PRD/SYS/exe/run/disp+work -v | grep -E "(kernel release|patch text|patch no.)"

# Output should confirm release patch level matching Note 3747649 requirements:
# kernel release  : 753
# patch level     : <patched_level_or_higher>

2. Message Server Trace Log Auditing

Inspect the Message Server trace file (dev_ms) located in /usr/sap/<SID>/<Instance>/work to detect unauthorized component registration attempts or node registration rejections post-patch.

# Search Message Server trace file for registration events
grep -iE "(MSConnect|MsSRegister|MsSUnregister|rejected)" /usr/sap/PRD/SCS00/work/dev_ms

3. Restricting Host OS User Privileges

Because exploitation attempts target the <sid>adm account, secure the host operating system context to limit post-exploitation escalation options:

  • Ensure <sid>adm lacks sudo permissions to switch to root without explicit authentication.
  • Enforce strict file permissions (chmod 750) on the /usr/sap/ filesystem tree to prevent unauthorized execution of local binary overwrites.
  • Enable SAP Security Audit Log (SAL) within transaction SM19 / SM20 to capture high-severity system events, HTTP request exceptions, and user logon failures.

Common Remediation Mistakes

  • Partial Kernel Updates: Updating the Primary Application Server (PAS) while failing to update central WEBDISP or standalone ASCS nodes leaves the landscape exposed to OVERPASS or S4GET.
  • Ignoring System Profiles: Failing to clean up old shadow kernel directories (/usr/sap/<SID>/SYS/exe/run) may result in instances falling back to unpatched binaries during unexpected system reboots.
  • Relying on Perimeter WAFs: Assuming edge WAFs block malformed EPP data while internal application ports remain directly accessible to network traffic.

Key Takeaways for SAP Systems Operations and Security Teams

The disclosure of CVE-2026-44756 and CVE-2026-58240 underlines the high operational risk associated with lower-layer kernel vulnerabilities in enterprise platforms. Security teams must transition away from treating SAP infrastructure as an isolated backend zone protected by perimeter network firewalls.

To systematically manage vulnerability exposure across enterprise SAP environments, operational teams should implement the following checklist:

Operational Milestone Responsible Team Action Required
Perimeter Assessment Network / Security Ops Identify all SAP Web Dispatchers and Message Server ports exposed to untrusted subnets or user VLANs.
Patch Staging SAP Basis Team Download binary updates defined in SAP Security Notes 3747649 and 3759472; verify cryptographic integrity.
Priority Patching SAP Basis Team Deploy kernel updates to SAP Web Dispatchers first, followed by ASCS/SCS Message Servers and Application Servers.
Post-Patch Audit Security Engineering Execute disp+work -v and review dev_ms trace logs to verify build numbers and monitor node registrations.
Trust Architecture Review Systems Architecture Re-evaluate internal net trust assumptions between application servers, central daemons, and client networks.

By prioritizing kernel updates, verifying binary builds, and restricting internal network access to administrative ports, organizations can successfully eliminate the high-severity exposure introduced by OVERPASS and S4GET.

Frequently asked questions

What is the difference between CVE-2026-44756 (OVERPASS) and CVE-2026-58240 (S4GET)?

CVE-2026-44756 (OVERPASS) is a CVSS 10.0 memory corruption flaw caused by missing boundary validation during Extended Passport (EPP) deserialisation in the SAP Kernel. CVE-2026-58240 (S4GET) is a CVSS 9.8 flaw caused by missing component authentication during instance registration in the SAP NetWeaver Message Server (component BC-CST-MS).

Can firewall rules protect SAP NetWeaver Message Server from CVE-2026-58240 without patching?

No. SAP GUI clients require direct network access to the Message Server port to receive load-balancing instructions during initial user logon. Blocking this port at a network firewall breaks legitimate user sessions across the enterprise, making host-level kernel patching mandatory.

What user permissions does an attacker gain upon exploiting these vulnerabilities?

Successful exploitation of either vulnerability grants the attacker unauthenticated remote operating system command execution under the privileges of the user running the SAP installation—typically the <sid>adm operating system account. This permits complete control over SAP process space, local files, and database access keys.

Which SAP Security Notes must be applied to mitigate OVERPASS and S4GET?

Organizations must apply SAP Security Note 3747649 to address CVE-2026-44756 (OVERPASS) and SAP Security Note 3759472 to address CVE-2026-58240 (S4GET). These notes contain updated binary packages for affected SAP Kernel releases and Web Dispatchers.

Does CVE-2026-44756 affect SAP Web Dispatcher deployments?

Yes. SAP Web Dispatcher releases 9.16, 9.18, 9.19, and 9.20 contain the vulnerable kernel code responsible for parsing Extended Passport headers. External-facing Web Dispatchers must be patched immediately to prevent perimeter entry into DMZ environments.

Sources and further reading

This article was drafted with AI assistance from the publicly cited sources and passed automated checks for structure and sourcing. Verify critical details against the vendor advisories linked above before acting.