Code execution via crafted DLL loading
Published Nov 11, 2025 · Updated Nov 11, 2025
DLL hijacking in Siemens Software Center before 3.5 and Solid Edge SE2025 before 225.0 Update 10 allows attackers to execute code. The applications search for and load a crafted DLL from an attacker-controlled filesystem location, but Siemens has not disclosed the DLL name, search path, or loading function. An attacker must place the DLL on the system and induce a legitimate user to launch the affected application; successful loading runs attacker code in that user's process.
Summary
What happened
DLL hijacking in Siemens Software Center before 3.5 and Solid Edge SE2025 before 225.0 Update 10 allows attackers to execute code. The applications search for and load a crafted DLL from an attacker-controlled filesystem location, but Siemens has not disclosed the DLL name, search path, or loading function. An attacker must place the DLL on the system and induce a legitimate user to launch the affected application; successful loading runs attacker code in that user's process.
The record
- CVE
- CVE-2025-40827
- Published
- Nov 11, 2025
- Updated
- Nov 11, 2025
- Vendor
- Siemens
- Product
- Solid Edge
- Classifications
- CWE-427, T1574.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 11, 2025CVE publishedPublication date reported by the CVE source.
- Nov 11, 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 <V225.0 Update 10
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