CVE-2025-41701: Beckhoff TE1000 | TwinCAT 3 Enineering · Deserialization of Untrusted Data
Affects Beckhoff TE1000 | TwinCAT 3 EnineeringSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Beckhoff TE1000 | TwinCAT 3 Enineering | Affected
| Fixed in– |
AI-suggested
1. Implement strict file handling policies: Restrict the opening of project files to trusted sources only. Educate users to verify the origin of project files before opening them. 2. Use application whitelisting and endpoint protection solutions that can detect and block suspicious behaviors triggered by deserialization exploits. 3. Isolate engineering workstations from general user networks and limit access to only authorized personnel to reduce exposure. 4. Employ least privilege principles: Users running TwinCAT 3 Engineering should operate with minimal necessary privileges to limit the impact of arbitrary command execution. 5. Monitor and audit usage of TwinCAT 3 Engineering for unusual activity, such as unexpected project file openings or command executions. 6. Coordinate with Beckhoff for timely patch releases and apply updates as soon as they become available. 7. Consider sandboxing or running the engineering tool in a controlled environment to contain potential exploitation. 8. Develop and enforce policies for secure transfer and storage of project files, including digital signatures or checksums to verify integrity.
Description
An unauthenticated attacker can trick a local user into executing arbitrary commands by opening a deliberately manipulated project file with an affected engineering tool. These arbitrary commands are executed in the user context.