Affects Siemens SIMOVE/SIPLANT industrial systems; unauthenticated file-read exposing keys/configs can disrupt OT operations across industries.
CVE-2026-67367
Unauthenticated directory traversal in Siemens SIMOVE/SIPLANT allows arbitrary file read.
Is CVE-2026-67367 being exploited?
Not confirmed. CVE-2026-67367 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.81% probability of exploitation in the next 30 days.
How severe is CVE-2026-67367?
CVE-2026-67367 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67367?
Yes. A fix has been recorded for CVE-2026-67367. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67367 affect?
CVE-2026-67367 affects SIMOVE Fleetmanager V3.1 (< V3.1.13), SIMOVE Fleetmanager V3.2 (< V3.2.4), SIMOVE Fleetmanager V3.3 (< V3.3.2), SIMOVE Fleetmanager V4.0 (< V4.0.1), and 4 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67367?
Apply Siemens fixes, isolate/limit HTTP access, and rotate exposed credentials/keys.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated directory traversal lets attackers read OS files (credentials, private keys, configs), enabling data theft and further compromise.
Immediate action required
- affected< V3.1.13
- affected< V3.2.4
- affected< V3.3.2
- affected< V4.0.1
- affected< *
- affected< *
- affected< *
- affected< V3.1.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.