dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-26661

HIGH · 8.8 CVSS v3.1 Published 2025-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 missing authorization check, SAP NetWeaver (ABAP Class Builder) allows an attacker to gain higher access levels than they should have, resulting in escalation of privileges. On successful exploitation, this could result in disclosure of highly sensitive information. It could also have a high impact on the integrity and 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

This is a missing authorization check vulnerability in SAP NetWeaver's ABAP Class Builder component. Attackers can exploit the lack of proper authorization validation to escalate their privileges beyond what their user account should permit, potentially accessing highly sensitive data and compromising system integrity and availability.

MitigationApply the SAP security patch for CVE-2025-26661 immediately, which implements proper authorization checks in the ABAP Class Builder. Conduct a thorough review of existing user authorizations to ensure they align with least-privilege principles after patch deployment.

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

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 ABAP system version
    Execute transaction SAINT or check system version via SAP GUI: System -> Status -> Component version, or use transaction SM51 to list server versions
    Affected if Running an unpatched SAP NetWeaver ABAP system where the security note for CVE-2025-26661 has not been applied
  2. Verify ABAP Class Builder component availability
    Attempt to access transaction SE24 (Class Builder) or SE80 (Object Navigator) - note if the transaction is accessible in the user's menu
    Affected if Class Builder transactions (SE24, SE80) are available to users without proper authorization checks in place
  3. Inspect user authorization roles for Class Builder
    Use transaction SUIM to search for roles containing authorization object S_BC_ABAPRESTSVC (or check if roles grant access to Class Builder without proper authorization objects). Run SU53 after failed authorization check to see missing authorizations
    Affected if User roles grant unrestricted access to ABAP Class Builder without proper authorization object checks being enforced
  4. Review recent security audit logs for Class Builder usage
    Check transaction SLG1 for Object: CLAS and Subobject: ABAP for recent Class Builder access, or review transaction SAAB for security audit logs related to ABAP repository changes
    Affected if Users are able to create, modify, or display ABAP classes without authorization failures being logged or blocked
  5. Confirm if security note for CVE-2025-26661 is applied
    Use transaction SNOTE to check if SAP Note 359xxxx (placeholder for CVE-2025-26661 note) is applied, or check transaction SPAM for the relevant support package containing the fix
    Affected if The specific security patch for this authorization check vulnerability has not been implemented in the system

A user is affected if they can access ABAP Class Builder (SE24/SE80) and perform operations without proper authorization validation, especially on unpatched SAP NetWeaver systems where the CVE-2025-26661 security note is not applied.

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 SAP security patch for CVE-2025-26661 immediately, which implements proper authorization checks in the ABAP Class Builder. Conduct a thorough review of existing user authorizations to ensure they align with least-privilege principles after patch deployment.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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