Skip to main content
CVE-2025-40815VulnerabilityPublished Updated

CVE-2025-40815: Siemens LOGO! 12/24RCE · Classic Buffer Overflow

Affects Siemens LOGO! 12/24RCESource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High : upgrade to 1.84.05 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.84.05
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Upgrade LOGO! 12/24RCE and LOGO! 12/24RCEo and LOGO! 230RCE and LOGO! 230RCEo and LOGO! 24CE and LOGO! 24CEo and LOGO! 24RCE and LOGO! 24RCEo and SIPLUS LOGO! 12/24RCE and SIPLUS LOGO! 12/24RCEo and SIPLUS LOGO! 230RCE and SIPLUS LOGO! 230RCEo and SIPLUS LOGO! 24CE and SIPLUS LOGO! 24CEo and SIPLUS LOGO! 24RCE and SIPLUS LOGO! 24RCEo to 1.84.05.

Affected software

ProductAffectedFixed in
SiemensLOGO! 12/24RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 12/24RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 230RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 230RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 24CEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 24CEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 24RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 24RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 12/24RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 12/24RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 230RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 230RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 24CEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 24CEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 24RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 24RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05

AI-suggested

1. Apply Siemens-provided patches immediately once available to address the buffer overflow vulnerability. 2. Restrict network access to affected PLCs by implementing strict firewall rules and network segmentation, isolating PLCs from general IT networks and the internet. 3. Employ deep packet inspection and anomaly detection systems to identify and block malformed TCP packets targeting PLCs. 4. Enforce strong authentication and access control policies to limit privileged user access, as exploitation requires high privileges. 5. Regularly audit and monitor network traffic to and from PLCs for suspicious activity. 6. Implement network intrusion detection systems (NIDS) tailored for industrial protocols to detect exploitation attempts. 7. Develop and test incident response plans specific to industrial control system compromises. 8. Educate operational technology (OT) personnel about this vulnerability and safe handling of Siemens LOGO! devices. 9. Consider deploying virtual patching or compensating controls if immediate patching is not feasible. 10. Maintain up-to-date asset inventories to quickly identify affected devices and prioritize remediation.

Description

A vulnerability has been identified in LOGO! 12/24RCE (6ED1052-1MD08-0BA2) (All versions < V1.84.05), LOGO! 12/24RCEo (6ED1052-2MD08-0BA2) (All versions < V1.84.05), LOGO! 230RCE (6ED1052-1FB08-0BA2) (All versions < V1.84.05), LOGO! 230RCEo (6ED1052-2FB08-0BA2) (All versions < V1.84.05), LOGO! 24CE (6ED1052-1CC08-0BA2) (All versions < V1.84.05), LOGO! 24CEo (6ED1052-2CC08-0BA2) (All versions < V1.84.05), LOGO! 24RCE (6ED1052-1HB08-0BA2) (All versions < V1.84.05), LOGO! 24RCEo (6ED1052-2HB08-0BA2) (All versions < V1.84.05), SIPLUS LOGO! 12/24RCE (6AG1052-1MD08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 12/24RCEo (6AG1052-2MD08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 230RCE (6AG1052-1FB08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 230RCEo (6AG1052-2FB08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 24CE (6AG1052-1CC08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 24CEo (6AG1052-2CC08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 24RCE (6AG1052-1HB08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 24RCEo (6AG1052-2HB08-7BA2) (All versions < V1.84.05). Affected devices do not properly validate the structure of TCP packets in several methods. This could allow an attacker to cause buffer overflows, get control over the instruction counter and run custom code.

References

Community reviews

Loading reviews…