# CVE-2026-22923: Memory corruption in NX

> A local attacker can exploit a data validation flaw during PDF export in Siemens NX to achieve arbitrary code execution.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Feb 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-whvv-qq52-jc5c

## What is CVE-2026-22923?

CVE-2026-22923 is a high-severity memory corruption vulnerability in Siemens NX, published on 10 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in NX (All versions < V2512), NX (Managed Mode) (All versions < V2512). The affected application contains a data validation vulnerability that could allow an attacker with local access to interfere with internal data during the PDF export process that could potentially lead to arbitrary code execution.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Siemens Nx.

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

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

## Is CVE-2026-22923 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22923 is a high-severity memory corruption vulnerability in Siemens NX, published on 10 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22923 in the wild and no public exploit code.

Affected product: Siemens NX. 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-22923/ (Markdown: https://insights.sbomify.com/CVE-2026-22923/index.md)
```

## Sources

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

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