CVE-2025-40816: Siemens LOGO! 12/24RCE · Missing Authentication
Affects Siemens LOGO! 12/24RCESource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 1.84.05 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.84.05
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 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
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
| Product | Affected | Fixed in |
|---|---|---|
| SiemensLOGO! 12/24RCE | Affected
| Fixed in
|
| SiemensLOGO! 12/24RCEo | Affected
| Fixed in
|
| SiemensLOGO! 230RCE | Affected
| Fixed in
|
| SiemensLOGO! 230RCEo | Affected
| Fixed in
|
| SiemensLOGO! 24CE | Affected
| Fixed in
|
| SiemensLOGO! 24CEo | Affected
| Fixed in
|
| SiemensLOGO! 24RCE | Affected
| Fixed in
|
| SiemensLOGO! 24RCEo | Affected
| Fixed in
|
| SiemensSIPLUS LOGO! 12/24RCE | Affected
| Fixed in
|
| SiemensSIPLUS LOGO! 12/24RCEo | Affected
| Fixed in
|
| SiemensSIPLUS LOGO! 230RCE | Affected
| Fixed in
|
| SiemensSIPLUS LOGO! 230RCEo | Affected
| Fixed in
|
| SiemensSIPLUS LOGO! 24CE | Affected
| Fixed in
|
| SiemensSIPLUS LOGO! 24CEo | Affected
| Fixed in
|
| SiemensSIPLUS LOGO! 24RCE | Affected
| Fixed in
|
| SiemensSIPLUS LOGO! 24RCEo | Affected
| Fixed in
|
AI-suggested
1. Siemens should prioritize releasing firmware updates or patches that implement proper authentication checks for critical functions, including network configuration changes. 2. If you cannot patch yet, organizations must isolate affected PLCs on segmented, trusted networks with strict access controls to prevent unauthorized remote access. 3. Implement network monitoring and anomaly detection to identify unexpected changes in device IP addresses or unauthorized configuration attempts. 4. Use firewalls and access control lists (ACLs) to restrict communication to and from LOGO! devices only to authorized management stations. 5. Employ VPNs or secure tunnels for remote access to industrial control systems to reduce exposure to adjacent network attackers. 6. Conduct regular audits of device configurations and network topology to detect unauthorized modifications promptly. 7. Train operational technology (OT) personnel to recognize signs of network manipulation and enforce strong physical security to prevent local tampering. 8. Develop incident response plans specific to industrial control system disruptions to minimize downtime in case of exploitation.
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 conduct certain validations when interacting with them. This could allow an unauthenticated remote attacker to manipulate the devices IP address, which means the device would not be reachable.