dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2026-40135

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An OS Command Injection vulnerability exists in the SAP NetWeaver Application Server for ABAP and ABAP Platform that allows an authenticated attacker with administrative access to execute specially crafted shell commands on the server, bypassing the logging mechanism. This allows the execution of unintended OS commands without detection, potentially impacting the integrity and availability of the application, with no impact on confidentiality.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OS Command Injection vulnerability in SAP NetWeaver Application Server for ABAP and ABAP Platform allows authenticated attackers with administrative privileges to execute arbitrary shell commands on the underlying OS, bypassing the logging mechanism to avoid detection. This compromises system integrity and availability while leaving no audit trail.

MitigationApply SAP security notes/patches for this vulnerability, review and restrict administrative access permissions, implement additional logging/monitoring for OS-level command execution, and conduct post-patch validation to confirm the injection vector is closed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Netweaver Application Server AbapApplication
Affected:= 700= 701= 702= 731= 740= 750= 751= 752= 753= 754= 755= 756

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP NetWeaver AS ABAP version
    Execute transaction SM51 or check system profile parameter 'saprel' via transaction RZ11. Alternatively, use transaction 'SAPSYSTEM' to retrieve the system number and check the kernel version in the /usr/sap/<SID>/SYS/exe/run directory.
    Affected if The installed version matches 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756.
  2. Verify administrative user access
    Review user assignments in transaction SU01 (User Maintenance) and check for users assigned to roles with broad administrative authorizations. Use transaction PFCG (Role Maintenance) to inspect roles containing authorization objects S_LOG_COM, S_RFC, or similar command execution-related authorizations.
    Affected if Multiple users exist with administrative privileges or roles granting extensive system control permissions.
  3. Check for OS command execution transactions
    Inspect transaction logs and authorizations for transactions that allow operating system command execution, such as SM69 (External Commands), SXPG_COMMAND_EXECUTE, or similar transaction codes. Review the authorization object S_LOG_COM for command execution rights.
    Affected if Users possess authorizations to execute external operating system commands through SAP transactions.
  4. Review audit logging configuration
    Examine system profile parameters for logging settings, specifically 'rsau/enable' and 'auditlog' configurations via transaction RZ10 or RZ11. Check if security audit log is active and review what events are being captured.
    Affected if Audit logging is disabled, set to minimal levels, or does not capture OS-level command execution events.

A system is affected if it runs SAP NetWeaver AS ABAP version 700-756 and has any user accounts with administrative privileges that include authorization to execute operating system commands through SAP transactions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security notes/patches for this vulnerability, review and restrict administrative access permissions, implement additional logging/monitoring for OS-level command execution, and conduct post-patch validation to confirm the injection vector is closed.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40135 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data