Skip to main content
VulnerabilityPublished

CVE-2025-41691: CODESYS Control RTE (SL) · NULL Pointer Dereference

Affects CODESYS Control RTE (SL)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 14 Nov 2026, 20:43 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
CODESYS Control RTE (SL)Affected
  • =3.5.21.10
Fixed in–

AI-suggested

  1. Immediate identification and inventory of all CODESYS Control RTE (SL) version 3.5.21.10 deployments within the organization.
  2. Apply vendor patches or updates as soon as they become available; monitor CODESYS advisories for official fixes.
  3. 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.
  4. Deploy intrusion detection/prevention systems (IDS/IPS) with signatures or anomaly detection capabilities tailored to detect malformed or suspicious communication requests targeting CODESYS protocols.
  5. Employ strict firewall rules to limit inbound traffic to only necessary sources and ports used by CODESYS Control RTE.
  6. Conduct regular security assessments and penetration tests focusing on industrial control systems to identify potential exploitation attempts.
  7. Establish robust incident response plans specific to OT environments to quickly respond to DoS events affecting control systems.
  8. Train operational staff to recognize signs of system instability or crashes that may indicate exploitation attempts.
  9. 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.

References

Community reviews

Loading reviews…