dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-34256

HIGH · 7.1 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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 ERP and SAP S/4HANA (Private Cloud and On-Premise), an authenticated attacker could execute a particular ABAP report to overwrite any existing eight?character executable ABAP report without authorization. If the overwritten report is subsequently executed, the intended functionality could become unavailable. Successful exploitation impacts availability, with a limited impact on integrity confined to the affected report, while confidentiality remains unaffected.

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

A missing authorization check in SAP ERP and SAP S/4HANA (Private Cloud and On-Premise) allows authenticated attackers to execute a specific ABAP report that can overwrite any existing eight-character executable ABAP report without proper authorization. When the tampered report is subsequently executed, its intended functionality becomes unavailable, primarily impacting system availability with limited integrity impact confined to the affected report.

MitigationImplement proper authorization checks in the affected ABAP report execution mechanism to verify user permissions before allowing overwrites. Apply SAP security patches once available and review report authorization configurations.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 product and version
    Execute transaction SM51 or use SAP transaction SWO1 to check the SAP system name and release version. Confirm it is SAP ERP or SAP S/4HANA (Private Cloud or On-Premise).
    Affected if The system runs SAP ERP or SAP S/4HANA (Private Cloud or On-Premise) without the available security patch.
  2. Locate the vulnerable overwrite ABAP report
    Search ABAP report repository using transaction SE38 or SE80. Look for reports that contain functionality to overwrite or replace other ABAP reports. Since the specific report name is not disclosed, check for any custom or modified reports with write/replace capabilities on other reports.
    Affected if A report exists in the system that allows overwriting executable ABAP reports without authorization checks.
  3. Identify 8-character executable ABAP reports
    Use transaction SE38 or report RS_HIERACHY_CHECK to list executable ABAP reports (type 1 programs) with exactly 8-character names in the system.
    Affected if Executable ABAP reports with 8-character names exist and could be targeted for unauthorized overwrite.
  4. Check authorization for report overwrite functionality
    Use transaction SU53 immediately after attempting to execute the overwrite-capable report to check for missing authorizations. Also review authorization object S_PROGRAM (ABAP/4 program execution) and any custom authorization objects related to report modification.
    Affected if Users can execute the overwrite-capable report without proper authorization objects (such as S_PROGRAM with write/modify permissions) being checked.
  5. Review recent modifications to executable reports
    Use transaction SE03 (Transport Organizer) or check tables like TRDIR and REPOEXT to review recent changes to executable ABAP reports, especially those with 8-character names. Look for unexpected modifications outside normal change management.
    Affected if Executable ABAP reports have been modified without proper change tickets or authorization records.

A user is affected if they run SAP ERP or S/4HANA (Private Cloud or On-Premise) where an ABAP report allowing unauthorized overwrite of 8-character executable reports exists and lacks proper authorization checks.

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

Implement proper authorization checks in the affected ABAP report execution mechanism to verify user permissions before allowing overwrites. Apply SAP security patches once available and review report authorization configurations.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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