dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2026-27688

MEDIUM · 5.0 CVSS v3.1 Published 2026-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/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
Due to a missing authorization check in SAP NetWeaver Application Server for ABAP, an authenticated attacker with user privileges could read Database Analyzer Log Files via a specific RFC function module. The attacker with the necessary privileges to execute this function module could potentially escalate their privileges and read the sensitive data, resulting in a limited impact on the confidentiality of the information stored. However, the integrity and availability of the system are not affected.

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

This is an authorization bypass vulnerability in SAP NetWeaver Application Server for ABAP where a missing authorization check on a specific RFC function module allows authenticated users with standard user privileges to access Database Analyzer Log Files. The attacker could potentially escalate privileges and read sensitive data stored in these log files, resulting in limited confidentiality impact.

MitigationApply the relevant SAP security patch that implements proper authorization checks on the vulnerable RFC function module, and conduct a review of user authorizations to ensure least-privilege access principles.

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= 730= 731= 740= 750= 751= 752= 753= 754= 755

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

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

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. Determine installed SAP NetWeaver ABAP version
    Execute transaction SAINT or SM37 and look at the SAP System Information, or use transaction SWI1 with selection for system info. Alternatively, run ABAP program RSWBOINS to check kernel and component versions.
    Affected if The installed version matches any of: 700, 701, 702, 730, 731, 740, 750, 751, 752, 753, 754, or 755.
  2. Verify Database Analyzer transaction access
    Attempt to access transaction DB02 or DBACOCKPIT with a standard (non-privileged) user account that has only basic authorizations.
    Affected if The standard user can access DB02 or DBACOCKPIT without receiving an authorization error.
  3. Check RFC function module authorization
    Use transaction SUIM to search for RFC function modules related to Database Analyzer (such as RS Database Analyzer or DB02 related RFCs). Review the authorization object S_RFC for the affected function module.
    Affected if Standard users have authorization for the vulnerable RFC function module (authorization object S_RFC with activity 16 or higher for the function module).
  4. Inspect user authorization roles
    Use transaction SUIM or PFCG to examine the roles assigned to standard users. Check if any role contains authorization object S_TCODE for DB02 or authorization object S_RFC for Database Analyzer-related function modules without proper restrictions.
    Affected if Standard users possess roles that grant access to DB02 transaction or the vulnerable RFC function module.
  5. Review Database Analyzer log file accessibility
    Attempt to retrieve Database Analyzer log files using the RFC function module or through transaction DB02 with a standard user account.
    Affected if The standard user can read or download Database Analyzer log files containing sensitive system information.

A user is affected if their SAP NetWeaver ABAP version is one of the listed versions AND standard users can access Database Analyzer (DB02) or the vulnerable RFC function module without proper authorization restrictions.

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 the relevant SAP security patch that implements proper authorization checks on the vulnerable RFC function module, and conduct a review of user authorizations to ensure least-privilege access principles.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27688 — 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-27688 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