Code execution via unsanitized project security properties
Published Aug 12, 2025 · Updated Dec 9, 2025
Deserialization in Siemens engineering platforms allows local users to execute arbitrary code by opening a crafted project file. The applications fail to sanitize stored security properties before reconstructing them, allowing attacker-controlled data to trigger type confusion. Exploitation requires a user to open an untrusted project, and the resulting code runs within the affected application's security context.
Summary
What happened
Deserialization in Siemens engineering platforms allows local users to execute arbitrary code by opening a crafted project file. The applications fail to sanitize stored security properties before reconstructing them, allowing attacker-controlled data to trigger type confusion. Exploitation requires a user to open an untrusted project, and the resulting code runs within the affected application's security context.
The record
- CVE
- CVE-2025-40759
- Published
- Aug 12, 2025
- Updated
- Dec 9, 2025
- Vendor
- Siemens
- Product
- SIMATIC STEP 7
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2025CVE publishedPublication date reported by the CVE source.
- Dec 9, 2025Record 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 <*
- Affected versionversion=0 <V17 Update 9
- Affected versionversion=0 <V19 Update 4
- Affected versionversion=0 <V20 Update 4
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.
Weakness, pattern, technique
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