CVE-2025-40759
BaseFortify
Publication date: 2025-08-12
Last updated on: 2025-12-09
Assigner: Siemens AG
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| siemens | sinamics_startdrive | * |
| siemens | tia_portal_cloud | * |
| siemens | simocode_es | * |
| siemens | step_7 | * |
| siemens | simotion_scout_tia | * |
| siemens | wincc | * |
| siemens | s7-plcsim | * |
| siemens | sirius_safety_es | * |
| siemens | sirius_soft_starter_es | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a deserialization flaw in multiple Siemens engineering platforms where the products do not properly sanitize stored security properties when parsing project files. This improper input handling can cause type confusion, allowing an attacker to execute arbitrary code within the affected applications. [1]
How can this vulnerability impact me? :
An attacker exploiting this vulnerability could execute arbitrary code within the affected Siemens applications, potentially leading to unauthorized control or disruption of industrial automation processes. This could compromise the integrity, availability, and confidentiality of the systems using these products. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves verifying the versions of affected Siemens products installed in your environment, such as SIMATIC STEP 7, SIMATIC WinCC, SIMOTION SCOUT TIA, and others listed. Since the vulnerability arises from improper sanitization of project files, monitoring for unexpected or unauthorized project file usage and suspicious activity within these applications is recommended. Siemens does not provide specific detection commands in the available resources. General best practices include checking software version numbers against known vulnerable versions and monitoring logs for unusual behavior related to project file parsing. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating affected Siemens products to the latest available versions where fixes exist, such as SIMATIC STEP 7 and SIMATIC WinCC versions starting from V19 Update 4, and SIMOTION SCOUT TIA versions from V5.6 SP1 HF7 onward. For products without available fixes, Siemens recommends only opening project files from trusted sources, protecting network access to devices, and configuring environments according to Siemens’ operational guidelines for Industrial Security. Applying these countermeasures reduces the risk of exploitation until patches are available. [1]