Code execution via X_T parser out-of-bounds read
Published Aug 11, 2026 · Updated Aug 11, 2026
Out-of-bounds read in Siemens Parasolid V38.0 before 38.0.235 and V38.1 before 38.1.230 allows attackers to execute code via crafted X_T files. The X_T file parser reads beyond a buffer boundary while decoding attacker-controlled model data; Siemens has not named the responsible function. Exploitation requires a user or embedding application to open the file, and successful code runs in the current process context; malformed input can instead crash it.
Summary
What happened
Out-of-bounds read in Siemens Parasolid V38.0 before 38.0.235 and V38.1 before 38.1.230 allows attackers to execute code via crafted X_T files. The X_T file parser reads beyond a buffer boundary while decoding attacker-controlled model data; Siemens has not named the responsible function. Exploitation requires a user or embedding application to open the file, and successful code runs in the current process context; malformed input can instead crash it.
The record
- CVE
- CVE-2026-64629
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Siemens
- Product
- Parasolid
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <V38.0.235
- Affected versionversion=0 <V38.1.230
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo