Targets Modbus TCP, a ubiquitous ICS protocol; exploitation can disrupt critical infrastructure and industrial operations.
CVE-2026-0667
Modbus TCP parsing flaw enables remote code execution, DoS, and data tampering on ICS devices.
Is CVE-2026-0667 being exploited?
Not confirmed. CVE-2026-0667 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.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-0667?
CVE-2026-0667 is rated Critical with a CVSS score of 9.3. 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-0667?
Not known from our data. No patch reference has been recorded for CVE-2026-0667, 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-0667 affect?
CVE-2026-0667 affects Modbus TCP-enabled devices, PLCs, RTUs, SCADA systems, and 2 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-0667?
Isolate Modbus devices, block TCP/502 from untrusted networks, apply vendor patches when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via Modbus TCP, denial of service, and loss of confidentiality/integrity on PLCs/SCADA.
Immediate action required
- affectedVersions prior to R3.4.2
- affectedVersions prior to R3.4.2 (Firmware version prior to 9.12.2)
- affectedVersions prior to R3.4.2 (Firmware version prior to 9.12.2)
- affectedAll Versions
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.