CVE intelligence and bounded remediation

CVE-2025-40945 — A vulnerability has been identified in COMOS V10.4.5 (All versions < V10.4.5.0.2), COMOS V10.6 (All versions < V10.6.1), Designcenter...

High CVSS 8.5

A vulnerability has been identified in COMOS V10.4.5 (All versions < V10.4.5.0.2), COMOS V10.6 (All versions < V10.6.1), Designcenter NX (All versions < V2512.7000), Simcenter 3D (All versions < V2512.7000), Simcenter Femap V2506 (All versions < V2506.0003), Simcenter Femap V2512 (All versions < V2512.0002), Simcenter Nastran (All versions < V2606), Simcenter STAR-CCM+ (All versions < V2606), Solid Edge SE2025 (All versions < V225.0 Update 13), Solid Edge SE2026 (All versions < V226.0 Update 04), Teamcenter Visualization V2412 (All versions < V2412.0012), Teamcenter Visualization V2506 (All versions < V2506.0009), Teamcenter Visualization V2512 (All versions < V2512.2605), Tecnomatix Plant Simulation V2404 (All versions < V2404.0022), Tecnomatix Plant Simulation V2504 (All versions < V2504.0010), Tecnomatix Process Simulate (All versions < V2606). Untrusted search path in IAM Client SDK may allow an authenticated user to potentially enable escalation of privilege via local access.

Severity
High
CVSS
8.5 (4.0)
Published
2026-07-14
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-426

Affected products

No browser-safe affected-product rows are available.

Matched remediation archetype

Supply-chain, dependency, build, and update integrity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
  • Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
  • Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.

Remediate safely

  • Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
  • Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
  • Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.