dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2026-24316

MEDIUM · 6.4 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 →
70/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
SAP NetWeaver Application Server for ABAP provides an ABAP Report for testing purposes, which allows to send HTTP requests to arbitrary internal or external endpoints. The report is therefore vulnerable to Server-Side Request Forgery (SSRF). Successful exploitation could lead to interaction with potentially sensitive internal endpoints, resulting in a low impact on data confidentiality and integrity. There is no impact on availability of the application.

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

SAP NetWeaver Application Server for ABAP contains a test ABAP report vulnerable to Server-Side Request Forgery (SSRF). The report allows unauthenticated or low-privileged users to send HTTP requests from the server to arbitrary internal or external endpoints, potentially accessing sensitive internal services and data.

MitigationDisable or remove the vulnerable ABAP test report from the production system and restrict execution permissions on similar diagnostic reports. Implement network segmentation to limit outbound connectivity from the SAP server.

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:= 740= 750= 752= 753= 754= 755= 756= 757= 758= 816= 918

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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. Verify SAP NetWeaver AS ABAP version
    Log into SAP system and run transaction SM51 or use ABAP report SAPSQL__VERSIONS to display the installed kernel version. Alternatively, use transaction SAINT to check installed support packages.
    Affected if The installed version matches one of the following: 740, 750, 752, 753, 754, 755, 756, 757, 758, 816, or 918
  2. Identify test diagnostic ABAP reports
    Use transaction SE38 or SE80 to search for ABAP reports in the system that are labeled as test, diagnostic, or diagnostic-related. Check common test report namespaces such as SAP* or $TMP development classes.
    Affected if A test or diagnostic ABAP report exists that can initiate HTTP requests and is accessible without proper authentication restrictions
  3. Verify report execution permissions
    Use transaction SU53 immediately after attempting to run any test report to check for missing authorizations. Also use transaction SUST to review authorization profiles assigned to users who can execute test reports.
    Affected if Users with low-privilege roles (such as SAP_ALL or broad test permissions) can execute reports that initiate outbound HTTP connections
  4. Confirm outbound HTTP access capability
    Check if the SAP system has the ability to make outbound HTTP calls by reviewing ICF (Internet Communication Framework) settings in transaction SICF. Look for active service nodes that permit HTTP client requests.
    Affected if The ICF HTTP client functionality is active and permits the server to initiate outbound HTTP requests to arbitrary endpoints

A user is affected if their SAP NetWeaver AS ABAP version matches the affected list and a test report with HTTP request capability is present and accessible to unauthenticated or low-privileged users.

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

Disable or remove the vulnerable ABAP test report from the production system and restrict execution permissions on similar diagnostic reports. Implement network segmentation to limit outbound connectivity from the SAP server.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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