# CVE-2026-120008: Memory Corruption Vulnerability in SAP NetWeaver (Internet Graphics Service)


- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-m4q3-78j7-767p

## What is CVE-2026-120008?

CVE-2026-120008 is a high-severity vulnerability in SAP_SE SAP NetWeaver (Internet Graphics Service), published on 10 Nov 2026. 

### Official description

SAP NetWeaver (Internet Graphics Service) does not sufficiently validate certain input values within incoming requests. An unauthenticated user could send a specially crafted request to trigger an out-of-bounds memory write in a worker process. Successful exploitation could result in memory corruption or repeated termination of the affected process, resulting in a high impact on availability and a low impact on integrity with no impact on confidentiality.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-120008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120008 is a high-severity vulnerability in SAP_SE SAP NetWeaver (Internet Graphics Service), published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120008 in the wild and no public exploit code.

Affected product: SAP_SE SAP NetWeaver (Internet Graphics Service). 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-120008/ (Markdown: https://insights.sbomify.com/CVE-2026-120008/index.md)
```

## Sources

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

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