CVE-2026-67873
Heap overflow in lib60870-C server FileSegment encoding enabling crash or RCE
Is CVE-2026-67873 being exploited?
Not confirmed. CVE-2026-67873 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.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-67873?
CVE-2026-67873 is rated Critical with a CVSS score of 9.8. 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-67873?
Not known from our data. No patch reference has been recorded for CVE-2026-67873, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-67873 affect?
CVE-2026-67873 affects lib60870-C 2.4.0, IEC 60870-5-104 servers using lib60870-C, SCADA/ICS devices and energy management systems. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67873?
Block/untrusted IEC 60870-5-104 access, deploy WAF/IDS rules, and apply vendor/library patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can send crafted ASDU/FileSegment to trigger a heap overflow, causing service crash or remote code execution on servers using lib60870-C 2.4.0.
Immediate action required