CVE-2025-41691: CODESYS Control RTE (SL) · NULL Pointer Dereference
Affects CODESYS Control RTE (SL)Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 14 Nov 2026, 20:43 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 14 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CODESYS Control RTE (SL) | Affected
| Fixed in– |
AI-suggested
- Immediate identification and inventory of all CODESYS Control RTE (SL) version 3.5.21.10 deployments within the organization.
- Apply vendor patches or updates as soon as they become available; monitor CODESYS advisories for official fixes.
- Implement network segmentation to isolate industrial control systems from general IT networks and restrict access to CODESYS Control RTE devices to trusted management networks only.
- Deploy intrusion detection/prevention systems (IDS/IPS) with signatures or anomaly detection capabilities tailored to detect malformed or suspicious communication requests targeting CODESYS protocols.
- Employ strict firewall rules to limit inbound traffic to only necessary sources and ports used by CODESYS Control RTE.
- Conduct regular security assessments and penetration tests focusing on industrial control systems to identify potential exploitation attempts.
- Establish robust incident response plans specific to OT environments to quickly respond to DoS events affecting control systems.
- Train operational staff to recognize signs of system instability or crashes that may indicate exploitation attempts.
- Consider temporary compensating controls such as disabling unnecessary communication interfaces or protocols on affected devices until patches are applied.
Description
An unauthenticated remote attacker may trigger a NULL pointer dereference in the affected CODESYS Control runtime systems by sending specially crafted communication requests, potentially leading to a denial-of-service (DoS) condition.