CVE-2025-41739: CODESYS PLCHandler · Out-of-bounds Read
Affects CODESYS PLCHandlerSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium.
Data as of 26 Oct 2026, 06:26 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CODESYS CODESYS PLCHandler | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-41739, European organizations should implement the following specific measures: 1) Immediately restrict network access to the CODESYS PLCHandler communication ports by applying strict firewall rules and network segmentation to isolate PLCs from untrusted networks. 2) Monitor network traffic for unusual or malformed socket communication patterns targeting the PLCHandler service, using intrusion detection systems (IDS) or industrial protocol analyzers. 3) Employ rate limiting or connection throttling on the communication servers to reduce the likelihood of successful race condition exploitation. 4) Coordinate with CODESYS vendors and subscribe to security advisories to obtain and apply patches promptly once released. 5) Conduct regular security assessments and penetration testing focused on industrial control system components to identify exposure. 6) Implement redundancy and failover mechanisms in critical control systems to minimize operational impact in case of service disruption. 7) Train operational technology (OT) staff to recognize signs of exploitation attempts and respond accordingly. These targeted actions go beyond generic advice by focusing on network-level controls, monitoring, and operational resilience specific to the nature of this vulnerability.
Description
An unauthenticated remote attacker, who beats a race condition, can exploit a flaw in the communication servers of the CODESYS Control runtime system on Linux and QNX to trigger an out-of-bounds read via crafted socket communication, potentially causing a denial of service.