CVE-2026-34256: SAP ERP and SAP S/4 HANA (Private Cloud and On-Premise) · Missing Authorization
Affects SAP ERP and SAP S/4 HANA (Private Cloud and On-Premise)Source CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SESAP ERP and SAP S/4 HANA (Private Cloud and On-Premise) | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict access to ABAP report execution to trusted and authorized users only, and monitor for unauthorized report modifications. Follow SAP's security recommendations once a vendor advisory is published.
Description
CVE-2026-34256 is a high-severity vulnerability in SAP ERP and SAP S/4HANA (Private Cloud and On-Premise) caused by a missing authorization check. An authenticated attacker can execute a specific ABAP report to overwrite any existing eight-character executable ABAP report without proper authorization. This can lead to the overwritten report becoming unavailable or altered in functionality when executed. The vulnerability impacts system availability significantly and has a limited impact on integrity confined to the affected report. Confidentiality is not affected. No official patch or remediation guidance is currently provided by the vendor, and no known exploits are reported in the wild.