dbcve.org
Improper Certificate ValidationWeakness · CWE-295

CVE-2025-40801

HIGH · 8.1 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 COMOS V10.6 (All versions < V10.6.1), COMOS V10.6 (All versions < V10.6.1), JT Bi-Directional Translator for STEP (All versions), NX V2412 (All versions < V2412.8900 with Cloud Entitlement (bundled as NX X)), NX V2506 (All versions < V2506.6000 with Cloud Entitlement (bundled as NX X)), Simcenter 3D (All versions < V2506.6000 with Cloud Entitlement (bundled as Simcenter X Mechanical)), Simcenter Femap (All versions < V2506.0002 with Cloud Entitlement (bundled as Simcenter X Mechanical)), Simcenter Studio (All versions < V2506.0001), Simcenter System Architect (All versions < V2506.0001), Tecnomatix Plant Simulation (All versions < V2504.0007). The SALT SDK is missing server certificate validation while establishing TLS connections to the authorization server. This could allow an attacker to perform a man-in-the-middle attack.

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 · high confidence

The SALT SDK (Siemens Authorization and License Token) in multiple Siemens industrial software products fails to validate SSL/TLS server certificates when establishing connections to authorization servers. This allows man-in-the-middle attackers to intercept encrypted communications, potentially hijack authentication sessions, or impersonate the authorization server.

MitigationApply the vendor-supplied version updates (COMOS V10.6.1, NX V2412.8900/V2506.6000, Simcenter V2506.6000/V2506.0002/V2506.0001, Tecnomatix V2504.0007) to enable proper certificate validation. For JT Bi-Directional Translator without a fixed version, ensure authorization server communication occurs over trusted/network-segmented paths.

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

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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. Identify installed Siemens industrial software
    Check system for installed Siemens products: COMOS, NX, Simcenter, or Tecnomatix. Look in Program Files/Siemens or check Windows Registry under HKLM\SOFTWARE\Siemens. Query installed programs via 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion'
    Affected if Any of these four products are installed without reaching patched versions
  2. Determine product version
    Locate the installed version number: for COMOS check C:\Program Files\Siemens\COMOS\version.txt or within the application Help > About; for NX check Help > About NX; for Simcenter check Help > About; for Tecnomatix check Help > About. Compare against: COMOS V10.6.1, NX V2412.8900, Simcenter V2506.6000, Tecnomatix V2504.0007
    Affected if Installed version is lower than the patched version for that product
  3. Verify SALT SDK is in use
    Check if the SALT SDK is configured or utilized. Look for SALT-related configuration files (salt.conf, salt_settings.xml) in the product installation directory or user config folders. Search for 'SALT' in log files or configuration directories under the product's workspace or project folders
    Affected if SALT SDK is configured or being used with an unpatched product version
  4. Inspect TLS connection behavior
    Use network monitoring tools (Wireshark, tcpdump) or system proxy settings to observe HTTPS connections from the Siemens product to authorization servers. Check if certificate validation occurs by testing with a self-signed certificate on a MITM proxy
    Affected if The product connects to authorization servers without rejecting invalid or fraudulent certificates (connections succeed despite certificate warnings)
  5. Check for authorization server configuration
    Examine product configuration files for authorization server URLs. Look in config directories for files containing 'auth', 'authorization', 'oauth', 'token', or server endpoints like '/oauth/token' or '/authorize'
    Affected if An authorization server is configured and the product version is unpatched

A defender is affected if any of COMOS, NX, Simcenter, or Tecnomatix are installed at versions below V10.6.1, V2412.8900, V2506.6000, or V2504.0007 respectively, AND the SALT SDK is being used to connect to an authorization server without proper certificate validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied version updates (COMOS V10.6.1, NX V2412.8900/V2506.6000, Simcenter V2506.6000/V2506.0002/V2506.0001, Tecnomatix V2504.0007) to enable proper certificate validation. For JT Bi-Directional Translator without a fixed version, ensure authorization server communication occurs over trusted/network-segmented paths.

Recommended fix Moderate confidence

Product-specific: COMOS V10.6.1, NX V2412.8900, NX V2506.6000, Simcenter 3D V2506.6000, Simcenter Femap V2506.0002, Simcenter Studio V2506.0001, Simcenter System Architect V2506.0001, Tecnomatix Plant Simulation V2504.0007

  1. For COMOS V10.6: Upgrade to V10.6.1 or later
  2. For NX V2412 with Cloud Entitlement (NX X): Upgrade to V2412.8900 or later
  3. For NX V2506 with Cloud Entitlement (NX X): Upgrade to V2506.6000 or later
  4. For Simcenter 3D with Cloud Entitlement (Simcenter X Mechanical): Upgrade to V2506.6000 or later
  5. For Simcenter Femap with Cloud Entitlement (Simcenter X Mechanical): Upgrade to V2506.0002 or later
  6. For Simcenter Studio: Upgrade to V2506.0001 or later
  7. For Simcenter System Architect: Upgrade to V2506.0001 or later
  8. For Tecnomatix Plant Simulation: Upgrade to V2504.0007 or later

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
40.0 hours of engineering $6,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40801 — 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-2025-40801 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