dbcve.org
CWE-426Weakness · CWE-426

CVE-2025-40945

MEDIUM · 6.7 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click 6 weeks old

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.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.

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

Untrusted search path vulnerability in IAM Client SDK allows an authenticated local user to potentially escalate privileges by placing malicious executables in the application search path that get loaded during runtime.

MitigationUpdate all affected Siemens software products to their patched versions as specified in the vendor advisory to remediate the untrusted search path in IAM Client SDK.

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

CVSS:3.1/AV:L/AC:L/PR:H/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 IAM Client SDK installation
    Search for IAM Client SDK files in common installation directories such as C:\Program Files\Siemens or C:\Program Files (x86)\Siemens, or use system inventory tools to detect Siemens software packages.
    Affected if IAM Client SDK from Siemens is present on the system.
  2. Determine installed SDK version
    Locate the IAM Client SDK version file (typically named version.txt, about.txt, or embedded in DLL properties) within the installation directory, or query installed programs through Windows Control Panel or PowerShell Get-Package.
    Affected if The installed version cannot be determined or is older than the patched version referenced in the Siemens vendor advisory.
  3. Review application search path configuration
    Examine the PATH environment variable and any application-specific path configurations in IAM Client SDK startup scripts or configuration files to identify directories searched during executable loading.
    Affected if The search path includes user-writable directories such as temp folders, working directories, or network shares accessible to authenticated local users.
  4. Check file permissions on search path directories
    Use icacls or Get-Acl commands to inspect write permissions on each directory listed in the application's search path, focusing on directories that are not owned by trusted administrators.
    Affected if Authenticated local users have write access to any directory in the application's executable search path.

A user is affected if IAM Client SDK is installed with a version prior to the patched release and the application search path contains directories writable by authenticated local users, allowing them to place malicious executables for privilege escalation.

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 Siemens software products to their patched versions as specified in the vendor advisory to remediate the untrusted search path in IAM Client SDK.

Recommended fix High confidence

Upgrade each affected product to the specific version listed in the advisory (e.g., COMOS V10.4.5.0.2, Simcenter Nastran V2606, Solid Edge SE2025 V225.0 Update 13, etc.)

  1. Identify which of the affected Siemens products (COMOS, Designcenter NX, Simcenter 3D, Simcenter Femap, Simcenter Nastran, Simcenter STAR-CCM+, Solid Edge SE2025, Solid Edge SE2026, Teamcenter Visualization, Tecnomatix Plant Simulation, Tecnomatix Process Simulate) you have deployed and note its current version.
  2. Locate the corresponding fixed version for that product as specified in the advisory: COMOS V10.4.5 < V10.4.5.0.2, COMOS V10.6 < V10.6.1, Designcenter NX < V2512.7000, Simcenter 3D < V2512.7000, Simcenter Femap V2506 < V2506.0003, Simcenter Femap V2512 < V2512.0002, Simcenter Nastran < V2606, Simcenter STAR-CCM+ < V2606, Solid Edge SE2025 < V225.0 Update 13, Solid Edge SE2026 < V226.0 Update 04, T
  3. Download the required version from the Siemens PLM Customer Portal or your local software distribution channel.
  4. Back up the existing installation, including configuration files and databases as recommended by the product documentation.
  5. Stop any running services or processes for the product before upgrading.
  6. Install the new version following the standard upgrade procedure for the product (run the installer, apply any patches, and update the IAM Client SDK component if presented).
  7. After installation, verify that the IAM Client SDK is updated to the version that includes the fix for CVE-2025-40945.
  8. Restart the product services and perform functional tests to ensure normal operation.
Caveat Review the release notes for each product before upgrading; some configurations or workflows may need adjustment.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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