Subscriber crash via nested-length boundary over-read
Published Jul 30, 2026 · Updated Jul 30, 2026
Out-of-bounds read in MZ Automation libIEC61850 before 1.6.2 allows attackers to crash a GOOSE subscriber via a multicast frame. The GOOSE payload parser accepts an attacker-controlled inner element length that exceeds its enclosing length and reads one byte past the boundary. A single unauthenticated Layer 2 multicast frame on the process bus terminates the subscriber process, interrupting service.
Summary
What happened
Out-of-bounds read in MZ Automation libIEC61850 before 1.6.2 allows attackers to crash a GOOSE subscriber via a multicast frame. The GOOSE payload parser accepts an attacker-controlled inner element length that exceeds its enclosing length and reads one byte past the boundary. A single unauthenticated Layer 2 multicast frame on the process bus terminates the subscriber process, interrupting service.
The record
- CVE
- CVE-2026-66364
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- MZ Automation GmbH
- Product
- libIEC61850
- Classifications
- CWE-125, T0814
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.6.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo