CVE-2025-41728: Beckhoff.Device.Manager.XAR · Out-of-bounds Read
Affects Beckhoff.Device.Manager.XARSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.5.3 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.3, 1.7.0.0, 0.0.5
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Jan 2026
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
Upgrade Beckhoff.Device.Manager.XAR to 2.5.3; MDP software package for TwinCAT/BSD to 1.7.0.0; MDP for Beckhoff RT Linux(R) to 0.0.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Beckhoff AutomationBeckhoff.Device.Manager.XAR | Affected
| Fixed in
|
| Beckhoff AutomationMDP software package for TwinCAT/BSD | Affected
| Fixed in
|
| Beckhoff AutomationMDP for Beckhoff RT Linux(R) | Affected
| Fixed in
|
AI-suggested
1. 2. Restrict network access to the Device Manager web service to trusted hosts and networks only, using firewalls and network segmentation to limit exposure. 3. Implement strict access controls and authentication mechanisms to minimize the number of users with low-level privileges capable of interacting with the vulnerable service. 4. Employ intrusion detection and prevention systems (IDS/IPS) with signatures or anomaly detection to identify suspicious requests targeting the Device Manager web service. 5. Conduct regular memory and process monitoring on systems running Beckhoff.Device.Manager.XAR to detect unusual memory access patterns or leaks. 6. Consider deploying application-layer gateways or proxies that can sanitize or block malformed requests before reaching the vulnerable service. 7. Document and audit all interactions with the Device Manager web service to facilitate incident response if exploitation is suspected. 8. Engage with Beckhoff Automation support for guidance and potential workarounds until official patches are released.
Description
A low privileged remote attacker may be able to disclose confidential information from the memory of a privileged process by sending specially crafted calls to the Device Manager web service that cause an out-of-bounds read operation under certain circumstances due to ASLR and thereby potentially copy confidential information into a response.