# CVE-2026-120009: Code Injection vulnerability in SAP ABAP Developer Tools (AMDP Data Preview)


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-jxjx-3x5x-cr8v

## What is CVE-2026-120009?

CVE-2026-120009 is a high-severity vulnerability in SAP_SE SAP ABAP Developer Tools (AMDP Data Preview), published on 10 Nov 2026. 

### Official description

SAP ABAP Developer Tools (AMDP Data Preview) does not perform sufficient validation and authorization checks within certain affected functionality. An attacker with high privileges could submit specially crafted input to inject and execute arbitrary code on the system. Successful exploitation could allow the attacker to fully compromise the system, resulting in a high impact on confidentiality, integrity and availability.

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

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


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

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

## Is CVE-2026-120009 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120009 is a high-severity vulnerability in SAP_SE SAP ABAP Developer Tools (AMDP Data Preview), published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120009 in the wild and no public exploit code.

Affected product: SAP_SE SAP ABAP Developer Tools (AMDP Data Preview). 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-120009/ (Markdown: https://insights.sbomify.com/CVE-2026-120009/index.md)
```

## Sources

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

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