# CVE-2026-120010: Memory Corruption vulnerability in SAP NetWeaver Application Server (SAP Message Server)


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-789r-fg73-j6ch

## What is CVE-2026-120010?

CVE-2026-120010 is a high-severity vulnerability in SAP_SE SAP NetWeaver Application Server (SAP Message Server), published on 10 Nov 2026. 

### Official description

SAP NetWeaver Application Server (SAP Message Server) does not properly size memory allocations when handling certain HTTP requests. An unauthenticated attacker could send a specially crafted request to trigger a heap buffer overflow in affected functionality. Successful exploitation causes the component to abort and remain unavailable until it is restarted by the framework, resulting in a high impact on availability of the system. There is no impact on confidentiality and integrity of the application.

Weakness: CWE-131 (Incorrect Calculation of Buffer Size)

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


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

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

## Is CVE-2026-120010 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: SAP_SE SAP NetWeaver Application Server (SAP Message Server). 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-120010/ (Markdown: https://insights.sbomify.com/CVE-2026-120010/index.md)
```

## Sources

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

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