CVE-2026-40133: SAP S/4HANA Condition Maintenance · Missing Authorization
Affects SAP S/4HANA Condition MaintenanceSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% 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:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 12 May 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 S/4HANA Condition Maintenance | Affected
| Fixed in– |
AI-suggested
Until a patch is available, restrict access to SAP S/4HANA Condition Maintenance to trusted users only and review user privileges to minimize risk.
Description
CVE-2026-40133 is a medium severity vulnerability in SAP S/4HANA Condition Maintenance caused by a missing authorization check. An authenticated attacker could view and modify condition table records without proper permissions, impacting confidentiality and integrity at a low level. The vulnerability may also disrupt legitimate user access to these records, causing a low impact on application availability. The affected versions include S4CORE 102 through 109. There is no vendor-provided patch or official remediation guidance available at this time, and no known exploits have been reported in the wild.