dbcve.org
Solid Edge Se2024Web browser · Siemens

CVE-2025-40811

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
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 Solid Edge SE2024 (All versions < V224.0 Update 14), Solid Edge SE2025 (All versions < V225.0 Update 6). The affected applications contains an out of bounds read vulnerability while parsing specially crafted PRT files. This could allow an attacker to crash the application or execute code in the context of the current process.

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

An out-of-bounds read vulnerability exists in Solid Edge SE2024 and SE2025 when parsing specially crafted PRT files. This memory corruption issue in the file parsing logic can be triggered by opening a malicious PRT file, potentially allowing an attacker to crash the application or achieve code execution within the process context.

MitigationUpdate Solid Edge SE2024 to version V224.0 Update 14 or later, and SE2025 to version V225.0 Update 6 or later. Avoid opening untrusted PRT files from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Solid Edge Se2024Web browser
Affected:all versions= 224.0
Solid Edge Se2025Web browser
Affected:all versions= 225.0

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 Solid Edge version
    Open Solid Edge and navigate to Help > About Solid Edge, or check the installed version via Windows Programs and Features. Look for the version number (e.g., V224.0 or V225.0).
    Affected if The installed version is SE2024 V224.0 or earlier, or SE2025 V225.0 or earlier.
  2. Confirm PRT file handling is in use
    Determine if Solid Edge is used to open or process PRT part files. Check for recent PRT file activity or default file associations in the Solid Edge installation.
    Affected if The environment processes or opens PRT files using the affected Solid Edge versions.
  3. Check for untrusted PRT file sources
    Review file locations from which PRT files are opened. Look for PRT files from external sources, email attachments, or downloaded files that may be untrusted.
    Affected if Users routinely open PRT files from untrusted or unknown sources in the affected versions.

You are affected if Solid Edge SE2024 (versions up to V224.0) or SE2025 (versions up to V225.0) is installed and processes PRT files, particularly from untrusted sources.

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 Solid Edge SE2024 to version V224.0 Update 14 or later, and SE2025 to version V225.0 Update 6 or later. Avoid opening untrusted PRT files from unknown sources.

Recommended fix High confidence

Solid Edge SE2024: V224.0 Update 14 or later; Solid Edge SE2025: V225.0 Update 6 or later

  1. 1. Identify the currently installed Solid Edge version (SE2024 or SE2025)
  2. 2. For Solid Edge SE2024: Upgrade to V224.0 Update 14 or later
  3. 3. For Solid Edge SE2025: Upgrade to V225.0 Update 6 or later
  4. 4. Obtain the update from the official Siemens support portal or cert-portal.siemens.com
  5. 5. Apply the update following standard Siemens installation procedures
  6. 6. Verify the version update was successful before using the application

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

Fix this in Solid Edge Se2024 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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