Quick answers
- Is CVE-2026-45769 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45769 being exploited in the wild.
- How severe is CVE-2026-45769?
- High severity, with a CVSS score of 7.5, published 10 September 2026.
- Which products and versions are affected?
- OISF Suricata before 7.0.16, before 8.0.5.
- Is there a fix for CVE-2026-45769?
- 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-45769 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-45769?
- 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
The vulnerability exists in the IKEv2 parser component, where client transform state is stored without proper bounds or limits. An attacker can send repeated, crafted UDP packets that trigger unbounded allocation of memory resources (CWE-770, CWE-400). The attack is remotely triggerable via network traffic with no authentication or user interaction required. A successful exploit results in memory exhaustion, causing Suricata to become unavailable and unable to monitor or block threats. Patches are available in versions 7.0.16 and 8.0.5; alternatively, IKE parsing can be disabled or traffic can be selectively bypassed using firewall rules.
Affected products
- OISF Suricata before 7.0.16, before 8.0.5
Timeline
- 2026-05-19: disclosed
- 2026-05-19: patched: Versions 7.0.16 and 8.0.5 released