Quick answers
- Is CVE-2026-45762 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45762 being exploited in the wild.
- How severe is CVE-2026-45762?
- High severity, with a CVSS score of 7.5, published 10 September 2026.
- Which products and versions are affected?
- OISF Suricata prior to 7.0.16 and 8.0.5.
- Is there a fix for CVE-2026-45762?
- A patch was published on 2026-05-19: Versions 7.0.16 and 8.0.5 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45762 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-45762?
- Check whether you run OISF Suricata at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Suricata's IP defragmentation module failed to validate that a cached defragmentation tracker used the same IP address family (IPv4 or IPv6) as the current packet being processed. An attacker can send a sequence of crafted IPv4/IPv6 fragmented packets that cause an IPv6 fragment to be incorrectly associated with an IPv4 defragmentation tracker. When Suricata attempts to reassemble these mismatched fragments, the type confusion results in a remote, unauthenticated, crash. The attack is network-reachable with no privileges or user interaction required. Patches are available in versions 7.0.16 and 8.0.5. As a workaround, enabling AF_PACKET's defrag option in IDS mode may prevent these crafted packets from reaching Suricata.
Affected products
- OISF Suricata prior to 7.0.16 and 8.0.5
Timeline
- 2026-09-10: disclosed
- 2026-05-19: patched: Versions 7.0.16 and 8.0.5 released