# CVE-2026-27675: Code Injection vulnerability in SAP Landscape Transformation

> High-privileged attackers can inject arbitrary ABAP code and OS commands in SAP Landscape Transformation, leading to limited data modification.

- **Severity:** Low 2.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-rqv3-6h29-j2m3

## What is CVE-2026-27675?

CVE-2026-27675 is a low-severity code injection vulnerability in SAP_SE SAP Landscape Transformation, published on 14 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

SAP Landscape Transformation contains a vulnerability in an RFC-exposed function module that could allow a high privileged adversary to inject arbitrary ABAP code and operating system commands. Due to this, some information could be modified, but the attacker does not have control over kind or degree. This leads to a low impact on integrity, while confidentiality and availability are not impacted.

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

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


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

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

## Is CVE-2026-27675 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27675 is a low-severity code injection vulnerability in SAP_SE SAP Landscape Transformation, published on 14 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-27675 in the wild and no public exploit code.

Affected product: SAP_SE SAP Landscape Transformation. 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-27675/ (Markdown: https://insights.sbomify.com/CVE-2026-27675/index.md)
```

## Sources

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

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