dbcve.org
NxApplication · Siemens

CVE-2026-22923

HIGH · 7.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 2512.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A data validation vulnerability exists in NX and NX (Managed Mode) PDF export functionality across all versions prior to V2512. An attacker with local system access can manipulate internal data during the PDF export process, potentially achieving arbitrary code execution through the crafted PDF generation.

MitigationUpgrade NX to version V2512 or later to obtain the patched release.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NxApplication
Affected:< 2512.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Siemens NX version
    Open NX and navigate to Help > About Siemens NX, or check the installation directory for version information typically found in version.info or product version files
    Affected if The reported version is less than 2512.0 (e.g., V2509, V2506, earlier versions)
  2. Confirm NX (Managed Mode) version if applicable
    If running NX in Managed Mode, check the managed server or client version through the administration console or help/about dialog
    Affected if The managed mode version is less than 2512.0
  3. Verify PDF export functionality is accessible
    Attempt to access the PDF export feature in NX (File > Export > PDF or similar path) or check if PDF export modules are loaded in the installation
    Affected if PDF export feature is present and functional in the NX installation
  4. Assess local system access exposure
    Review which users have local system access to the machine running NX, check user group memberships (Administrators, Power Users) and terminal services/remote access configurations
    Affected if Multiple users or untrusted users have local system access to the NX workstation

You are affected if your Siemens NX installation (standalone or Managed Mode) is version below 2512.0 and the PDF export feature is accessible to users with local system access on that machine.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2512.0 or later
Fixed in 2512.0
Interim mitigation

Upgrade NX to version V2512 or later to obtain the patched release.

Recommended fix High confidence

V2512

  1. Verify current NX installation version by opening NX and checking Help > About NX, or using the NX launcher version information
  2. Download NX version 2512.0 or later from Siemens Support Portal (support.industry.siemens.com) or your organization's software distribution system
  3. Ensure all active NX sessions are closed before upgrading
  4. Run the NX installer with appropriate administrator privileges
  5. Follow the installation wizard prompts to complete the upgrade to version 2512.0 or later
  6. Verify the installed version matches the target version after installation completes
  7. Test PDF export functionality to confirm the vulnerability is remediated
Caveat Review release notes for V2512 for any changes to file formats, workflows, or system requirements that may affect existing projects

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22923 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22923 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data