# CVE-2025-40800: Security feature bypass in COMOS V10.6

> Missing TLS certificate validation in the IAM client allows attackers to perform man-in-the-middle attacks on Siemens engineering software.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-xg9v-jc69-p54f

## What is CVE-2025-40800?

CVE-2025-40800 is a critical vulnerability in Siemens COMOS V10.6, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-40800?


## How do I fix CVE-2025-40800?

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

## Is CVE-2025-40800 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40800 and fix it if it is affected.

What it is: CVE-2025-40800 is a critical vulnerability in Siemens COMOS V10.6, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40800 in the wild and no public exploit code.

Affected product: Siemens COMOS V10.6. 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-2025-40800/ (Markdown: https://insights.sbomify.com/CVE-2025-40800/index.md)
```

## Sources

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

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