# CVE-2025-26656: Missing Authorization check in S/4HANA (Manage Purchasing Info Records)

> An authenticated attacker can bypass authorization checks in the Manage Purchasing Info Records OData service to escalate privileges and modify data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 11 Mar 2025
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-734v-c3wv-7593

## What is CVE-2025-26656?

CVE-2025-26656 is a medium-severity missing authorization vulnerability in SAP_SE S/4HANA (Manage Purchasing Info Records), published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OData Service in Manage Purchasing Info Records does not perform necessary authorization checks for an authenticated user, allowing an attacker to escalate privileges. This has low impact on integrity of the application.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-26656?


## How do I fix CVE-2025-26656?

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

## Is CVE-2025-26656 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26656 and fix it if it is affected.

What it is: CVE-2025-26656 is a medium-severity missing authorization vulnerability in SAP_SE S/4HANA (Manage Purchasing Info Records), published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26656 in the wild and no public exploit code.

Affected product: SAP_SE S/4HANA (Manage Purchasing Info Records). 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-2025-26656/ (Markdown: https://insights.sbomify.com/CVE-2025-26656/index.md)
```

## Sources

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

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