Siemens LOGO! Soft Comfort has hardcoded crypto key
Siemens LOGO! Soft Comfort before V9 uses a hardcoded AES master key and unsalted password hashes, letting local attackers decrypt or crack project files.
Sourcecisa.gov — open the original
What to check
- Applies to
- The 2 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
Siemens has disclosed two vulnerabilities in LOGO! Soft Comfort, the configuration software for its LOGO! programmable logic controllers used across commercial facilities and transportation infrastructure worldwide. The first issue, CVE-2026-57262, stems from a static, hardcoded AES master key embedded in the application used to encrypt project files. A local attacker who extracts this key from application files or memory can decrypt project files or strip passwords entirely, bypassing the intended protection without ever knowing the legitimate password.
The second issue, CVE-2026-57263, involves the project password feature storing credentials as unsalted SHA-256 hashes. Anyone who obtains a project file can run efficient offline dictionary or brute-force attacks against the hash to recover the plaintext password, since the lack of salting removes the computational cost that salted hashing would normally impose. Both flaws require local access to exploit and primarily threaten confidentiality and integrity of PLC project logic and configuration data rather than enabling remote compromise.
Siemens has released LOGO! Soft Comfort V9 to address both issues, though a corresponding hardware upgrade to LOGO! V9 BM or later is also required — devices running in compatibility mode remain vulnerable even after the software update. CISA republished the Siemens ProductCERT advisory (SSA-751328) and reiterates standard ICS hardening guidance: minimizing network exposure, isolating control system networks behind firewalls, and using VPNs for remote access. No known exploitation in the wild has been reported.
Mentioned in this report
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-26-225-13
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs