dbcve.org
Solid Edge Se2024Web browser · Siemens

CVE-2025-40810

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

This is an out-of-bounds write vulnerability in Solid Edge's PRT file parser. Specially crafted PRT files can trigger the vulnerability, potentially allowing an attacker to achieve code execution within the application's context. The vulnerability affects SE2024 versions prior to V224.0 Update 14 and SE2025 versions prior to V225.0 Update 6.

MitigationApply vendor-supplied patches to update Solid Edge SE2024 to V224.0 Update 14 or later, and SE2025 to V225.0 Update 6 or later. Until patched, avoid opening untrusted PRT files from unknown or untrusted 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 go to Help > About Solid Edge, or right-click the SE2024/SE2025 executable and view Properties > Details to see the Product Version
    Affected if version shows SE2024 prior to V224.0 Update 14 or SE2025 prior to V225.0 Update 6
  2. Check Windows registry for version
    Examine the registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SolidEdge\Version or HKEY_CURRENT_USER\SOFTWARE\Siemens\SolidEdge\Version for the installed version value
    Affected if version value is below V224.0 Update 14 for SE2024 or below V225.0 Update 6 for SE2025
  3. Locate Solid Edge executable
    Find the main Solid Edge executable (usually at C:\Program Files\Siemens\SolidEdge<version>\Program\solidedge.exe) and check its file version property
    Affected if file version corresponds to a build prior to the patched updates
  4. Verify the vulnerability trigger condition
    This flaw is triggered when Solid Edge opens a specially crafted PRT file - this is the application's core function and requires no special configuration
    Affected if the installed version is vulnerable AND the application is used to open PRT files from untrusted sources

A user is affected if they have Solid Edge SE2024 version before V224.0 Update 14 or SE2025 version before V225.0 Update 6 installed, and they open untrusted PRT files with the application.

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

Apply vendor-supplied patches to update Solid Edge SE2024 to V224.0 Update 14 or later, and SE2025 to V225.0 Update 6 or later. Until patched, avoid opening untrusted PRT files from unknown or untrusted 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 current Solid Edge version by opening the application and checking Help > About Solid Edge
  2. 2. For Solid Edge SE2024 users: Download and install V224.0 Update 14 or later from Siemens' official support portal
  3. 3. For Solid Edge SE2025 users: Download and install V225.0 Update 6 or later from Siemens' official support portal
  4. 4. Verify the update was successful by checking the version in Help > About Solid Edge
  5. 5. Ensure the installed version meets or exceeds the minimum security update level for your product line
Caveat Point releases typically do not introduce breaking changes; this is a security patch

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

Fix this in Solid Edge Se2024 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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