Out-of-bounds ReadWeakness · CWE-125

CVE-2025-40936

HIGH · 7.8 CVSS v3.1 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 PS/IGES Parasolid Translator Component (All versions < V29.0.258), Simcenter Femap (All versions < V2512.0003), Solid Edge (All versions < V226.00 Update 03). The affected applications contains an out of bounds read vulnerability while parsing specially crafted IGS files. This could allow an attacker to crash the application or execute code in the context of the current process. (ZDI-CAN-26755)

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

This is an out-of-bounds read vulnerability in the IGES (IGS) file parser within Siemens Parasolid-based translation components used across multiple CAD products. When parsing specially crafted IGS files, the parser reads memory beyond allocated buffers, which can corrupt memory and potentially enable arbitrary code execution in the context of the running process.

MitigationUpdate affected software to vendor-supplied patched versions: PS/IGES Parasolid Translator to V29.0.258 or later, Simcenter Femap to V2512.0003 or later, and Solid Edge to V226.00 Update 03 or later. Until patches are applied, avoid opening IGS files from untrusted sources.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Parasolid-based CAD products
    Check program files for Simcenter Femap, Solid Edge, or Parasolid IGES Translator installations. Look for executables like femap.exe, sedge.exe, or ps_igs_translator.exe in typical install directories (C:\Program Files\Siemens or C:\Program Files\Femap).
    Affected if Any of these Siemens CAD products are installed on the system
  2. Determine installed product version
    For Solid Edge: Open the application, go to Help > About Solid Edge to view the version (e.g., V226.00). For Simcenter Femap: Go to Help > About Femap. For Parasolid Translator: Check the application's About dialog or the executable's properties (right-click exe > Properties > Details).
    Affected if Version is 29.0.258 or prior for Parasolid Translator, 2512.0003 or prior for Simcenter Femap, or 226.00 Update 03 or prior for Solid Edge
  3. Verify IGS file handling capability is present
    Check if the Parasolid IGES translator module is available. Look for IGS file association in the system (search for .igs or .ige files in the product's translator or import folders), or check the product's import/export file format list includes IGES (.igs, .ige).
    Affected if IGES/IGS file format support is present in the installed product
  4. Confirm active use of IGES parser
    Review recent file open operations or scan the system for .igs/.ige files that may have been opened with the affected product. Check application logs or recent documents if available.
    Affected if The product has been used to open IGS files, enabling the vulnerable parser code path

The environment is affected if any of the three products (Parasolid IGES Translator, Simcenter Femap, or Solid Edge) are installed with versions at or below the patched versions and IGES file import capability is present.

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 affected software to vendor-supplied patched versions: PS/IGES Parasolid Translator to V29.0.258 or later, Simcenter Femap to V2512.0003 or later, and Solid Edge to V226.00 Update 03 or later. Until patches are applied, avoid opening IGS files from untrusted sources.

Recommended fix High confidence

PS/IGES Parasolid Translator Component V29.0.258 | Simcenter Femap V2512.0003 | Solid Edge V226.00 Update 03

  1. Identify which Siemens product(s) are in use: PS/IGES Parasolid Translator Component, Simcenter Femap, or Solid Edge
  2. For PS/IGES Parasolid Translator Component: upgrade to version V29.0.258 or later
  3. For Simcenter Femap: upgrade to version V2512.0003 or later
  4. For Solid Edge: upgrade to version V226.00 Update 03 or later
  5. Obtain the updated version from official Siemens channels (Siemens Support Center or software update mechanism)
  6. After installation, verify the version matches or exceeds the fixed release
  7. Test with legitimate IGS/IGES files to ensure normal functionality
Caveat Security update with version bumps; no functional breaking changes expected for normal CAD operations

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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