CVE Intelligence
High Memory corruption

CVE-2026-50059 — Out-of-bounds Write in Siemens Solid Edge Se2025

A vulnerability has been identified in Solid Edge SE2025 (All versions < V225.0 Update 15), Solid Edge SE2026 (All versions < V226.0 Update 7). The affected applications contains an out of bounds write vulnerability while parsing specially crafted DFT files. This could allow an attacker to execute code in the context of the current process.

Published Aug 11, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database · CNA: productcert@siemens.com

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Siemens
Solid Edge Se2025 and 1 more
CVSS base
7.8
High · 1 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Siemens Solid Edge Se2025, Siemens Solid Edge Se2026).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Siemens Solid Edge Se2025 version 225.0-update_0001version 225.0-update_0014version 225.0-update_0013version 225.0-update_0012version 225.0-update_0011version 225.0-update_0010version 225.0-update_0009version 225.0-update_0008
and 7 more version 225.0-update_0007version 225.0-update_0006version 225.0-update_0005version 225.0-update_0004version 225.0-update_0003version 225.0-update_0002version 225.0
Vulnerable NIST National Vulnerability Database
Siemens Solid Edge Se2026 version 226.0version 226.0-update_1version 226.0-update_2version 226.0-update_3version 226.0-update_4version 226.0-update_5version 226.0-update_6 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.3 CVSS 4.0 High — — productcert@siemens.com via NIST National Vulnerability Database
7.8 CVSS 3.1 High 1.8 5.9 productcert@siemens.com via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: productcert@siemens.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • CVSS changed · 7.8
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Aug 11, 2026 · productcert@siemens.com

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

Elsewhere on this site

Siemens
every CVE for this vendor
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-50063 Out-of-bounds Read in Siemens Solid Edge Se2025 Aug 11, 2026
  • High CVE-2026-50060 Use After Free in Siemens Solid Edge Se2025 Aug 11, 2026
  • High CVE-2026-50061 Use After Free in Siemens Solid Edge Se2025 Aug 11, 2026
  • High CVE-2026-50062 Out-of-bounds Read in Siemens Solid Edge Se2025 Aug 11, 2026
  • High CVE-2026-50064 Out-of-bounds Write in Siemens Solid Edge Se2025 Aug 11, 2026
  • High CVE-2026-50058 Out-of-bounds Read in Siemens Solid Edge Se2025 Aug 11, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-50059 is "Out-of-bounds Write in Siemens Solid Edge Se2025", rated High. It affects Solid Edge Se2025 (Siemens); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.