# CVE-2026-27677: Missing Authorization check in SAP S/4HANA OData Service (Manage Reference Equipment)

> Attackers can update and delete reference equipment entities without authorization, compromising data integrity in SAP S/4HANA.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 14 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-58xj-93qq-mmvg

## What is CVE-2026-27677?

CVE-2026-27677 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA OData Service (Manage Reference Equipment), published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to missing authorization checks in the SAP S/4HANA OData Service (Manage Reference Equipment), an attacker could update and delete child entities via OData services without proper authorization. This vulnerability has a high impact on integrity, while confidentiality and availability are not impacted.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-27677 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27677 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA OData Service (Manage Reference Equipment), published on 14 Apr 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-27677 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA OData Service (Manage Reference Equipment). 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-27677/ (Markdown: https://insights.sbomify.com/CVE-2026-27677/index.md)
```

## Sources

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

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