# CVE-2026-89121: Missing Authorization Check in SAP S/4HANA (Linear Asset Management RAP Business Object)

> Low-privilege local attackers can bypass authorization checks to modify unauthorized business object data in SAP S/4HANA.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-hj55-fc48-cj53

## What is CVE-2026-89121?

CVE-2026-89121 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Linear Asset Management RAP Business Object), published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SAP S/4HANA does not perform sufficient instance-level authorization checks for certain modification operations on associated business object data. An attacker with low privileges and local access to the system could bypass authorization checks to modify data belonging to objects they are not authorized for. This results in a high impact on integrity. There is no impact on confidentiality and availability.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-89121 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89121 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Linear Asset Management RAP Business Object), published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89121 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA (Linear Asset Management RAP Business Object). 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-89121/ (Markdown: https://insights.sbomify.com/CVE-2026-89121/index.md)
```

## Sources

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

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