# CVE-2025-27429: Code Injection Vulnerability in SAP S/4HANA (Private Cloud or On-Premise)

> An attacker with user privileges can inject arbitrary ABAP code via RFC, bypassing authorization checks and risking 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:** 8 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-87hf-jhfp-wp4g

## What is CVE-2025-27429?

CVE-2025-27429 is a critical code injection vulnerability in SAP_SE SAP S/4HANA (Private Cloud), published on 8 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP S/4HANA allows an attacker with user privileges to exploit a vulnerability in the function module exposed via RFC. This flaw enables the injection of arbitrary ABAP code into the system, bypassing essential authorization checks. This vulnerability effectively functions as a backdoor, creating the risk of full system compromise, undermining the confidentiality, integrity and availability of the system.

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

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


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

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

## Is CVE-2025-27429 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27429 is a critical code injection vulnerability in SAP_SE SAP S/4HANA (Private Cloud), published on 8 Apr 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-27429 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA (Private Cloud). 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-27429/ (Markdown: https://insights.sbomify.com/CVE-2025-27429/index.md)
```

## Sources

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

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