dbcve.org
Improper Certificate ValidationWeakness · CWE-295

CVE-2025-40800

HIGH · 7.4 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 →
83/100
Remediation priority · High
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), NX V2412 (All versions < V2412.8700), NX V2506 (All versions < V2506.6000), Simcenter 3D (All versions < V2506.6000), Simcenter Femap (All versions < V2506.0002), Solid Edge SE2025 (All versions < V225.0 Update 10), Solid Edge SE2026 (All versions < V226.0 Update 1). The IAM client in affected products 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 IAM client in affected Siemens products (COMOS, NX, Simcenter 3D, Simcenter Femap, Solid Edge) does not validate server certificates when establishing TLS connections to the authorization server. This allows an attacker to intercept communications via a man-in-the-middle attack and potentially steal credentials or hijack authentication sessions.

MitigationUpdate all affected products to their fixed versions: COMOS V10.6.1+, NX V2412.8700+, NX V2506.6000+, Simcenter 3D V2506.6000+, Simcenter Femap V2506.0002+, Solid Edge SE2025 Update 10+, Solid Edge SE2026 Update 1+.

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
None

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

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 product
    Check system for any of these products: COMOS, NX, Simcenter 3D, Simcenter Femap, or Solid Edge. Look in Program Files/Siemens or check installed programs list.
    Affected if Any of these products are installed, proceed to version check
  2. Determine product version
    Open the installed Siemens product and navigate to Help > About or use the application's version information dialog. For COMOS, check the COMOS version in the startup screen or via the version info in the program directory.
    Affected if Version is below the fixed version for that product
  3. Compare against affected version ranges
    Compare your installed version to these thresholds: COMOS below V10.6.1, NX below V2412.8700 or below V2506.6000, Simcenter 3D below V2506.6000, Simcenter Femap below V2506.0002, Solid Edge SE2025 below Update 10 or SE2026 below Update 1.
    Affected if Installed version falls below any of these fixed versions for your product
  4. Confirm IAM client usage
    Verify if the product connects to an authorization/authentication server. This is typically configured in the product's license manager or IAM settings. Check if network connections to authorization endpoints are active.
    Affected if The IAM client feature is in use and connects to an authorization server, the vulnerability is present in unpatched versions

You are affected if any of these Siemens products (COMOS, NX, Simcenter 3D, Simcenter Femap, Solid Edge) are installed with a version below the fixed versions AND the product uses IAM-based authentication to a server.

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

Update all affected products to their fixed versions: COMOS V10.6.1+, NX V2412.8700+, NX V2506.6000+, Simcenter 3D V2506.6000+, Simcenter Femap V2506.0002+, Solid Edge SE2025 Update 10+, Solid Edge SE2026 Update 1+.

Recommended fix High confidence

COMOS V10.6.1, NX V2412.8700, NX V2506.6000, Simcenter 3D V2506.6000, Simcenter Femap V2506.0002, Solid Edge SE2025 V225.0 Update 10, Solid Edge SE2026 V226.0 Update 1

  1. Identify the specific Siemens product from the list: COMOS, NX, Simcenter 3D, Simcenter Femap, or Solid Edge
  2. Locate the current installed version of the affected product
  3. Upgrade to the fixed version as specified for your product: COMOS to V10.6.1, NX V2412 to V2412.8700, NX V2506 to V2506.6000, Simcenter 3D to V2506.6000, Simcenter Femap to V2506.0002, Solid Edge SE2025 to V225.0 Update 10, or Solid Edge SE2026 to V226.0 Update 1
  4. After upgrade, verify that the IAM client now validates server certificates during TLS connections to the authorization server
  5. Test the TLS connection to the authorization server to confirm proper certificate validation is functioning

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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