# CVE-2026-40133: Missing Authorization check in SAP S/4HANA Condition Maintenance

> An authenticated attacker can view and modify condition table records in SAP S/4HANA due to missing authorization checks, impacting data confidentiality and integrity.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-gqmf-q62p-q4q6

## What is CVE-2026-40133?

CVE-2026-40133 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA Condition Maintenance, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to missing authorization check in SAP S/4HANA Condition Maintenance, an authenticated attacker could gain unauthorized access to view and modify condition table records, resulting in low impact on the confidentiality and integrity of the data. Additionally, this vulnerability may prevent the legitimate user from accessing the records, causing low impact on application availability.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-40133?


## How do I fix CVE-2026-40133?

No fix has been published for CVE-2026-40133 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40133 being exploited?

There is no known exploitation of CVE-2026-40133 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40133 and fix it if it is affected.

What it is: CVE-2026-40133 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA Condition Maintenance, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40133 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA Condition Maintenance. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40133/ (Markdown: https://insights.sbomify.com/CVE-2026-40133/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40133
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40133
- OSV: https://osv.dev/vulnerability/CVE-2026-40133

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40133/
Summaries are generated and may contain mistakes; the official description above is the record.