# CVE-2026-89107: Code Injection vulnerability in SAP S/4HANA (Manage Substitution/Validation Rules)

> An authenticated attacker with specific privileges can inject executable ABAP code via rule definitions, leading to full system compromise.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-mw39-66pq-v675

## What is CVE-2026-89107?

CVE-2026-89107 is a critical code injection vulnerability in SAP_SE SAP S/4HANA (Manage Substitution/Validation Rules), published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP S/4HANA (Manage Substitution/Validation Rules) does not sufficiently validate input processed by rule definition functionality that utilizes a domain-specific scripting language. An authenticated attacker with specific business privileges could submit specially crafted input, which is interpreted as executable ABAP code by the rule processing logic. Successful exploitation could allow the attacker to execute ABAP arbitrary code into the system, resulting in full compromise of the affected system and high impact on confidentiality, integrity, and availability of the system.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-89107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89107 is a critical code injection vulnerability in SAP_SE SAP S/4HANA (Manage Substitution/Validation Rules), published on 13 Oct 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-89107 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA (Manage Substitution/Validation Rules). 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-89107/ (Markdown: https://insights.sbomify.com/CVE-2026-89107/index.md)
```

## Sources

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

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