CVE-2026-45769

ikev2: unbounded client transform storage can lead to resource exhaustion

Published Sep 10, 2026 CVSS 3.1 · 7.5 High EPSS 1.8% KEV · Not listed
Description
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to versions 7.0.16 and 8.0.5,IKEv2 parser state could grow without bounds while storing client transforms. Repeated crafted UDP traffic may cause Suricata to consume excessive memory, potentially resulting in denial of service. Versions 7.0.16 and 8.0.5 fix the issue. Some workarounds are available. Disable IKE application-layer parsing if it is not needed. Alternatively, use a rule to bypass ike flows after the first packets like `alert ike any any -> any any (sid: 2; flow.pkts_toserver: > 256; bypass; noalert;)`.

Analysis

AI-generated

Technical impact

Suricata, an IDS/IPS engine, has a flaw that allows an attacker to send crafted UDP packets that cause the IKEv2 parser to store client transform data without bounds. This leads to arbitrary memory growth in Suricata, which can exhaust available resources and cause the engine to stop responding, resulting in a denial of service.

Affected Systems

Affected systems include Suricata installations using versions earlier than 7.0.16 in the 7.x line or earlier than 8.0.5 in the 8.x line, all distributed by the Open Information Security Foundation.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity; the EPSS score of 1% indicates a low exploitation probability, and the vulnerability is not yet in the CISA KEV catalog. Exploitation requires sending crafted UDP traffic to the Suricata instance, potentially from any remote host, which can cause the engine to exhaust memory and become unresponsive.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Suricata to at least version 7.0.16 or 8.0.5.
  • If an upgrade is not possible, disable IKEv2 application-layer parsing in the Suricata configuration to prevent the vulnerable parsing logic from executing.
  • Use a rule to bypass IKE flows after the first packet, for example: alert ike any any -> any any (sid: 2; flow.pkts_toserver: > 256; bypass; noalert;).
  • Optionally monitor Suricata’s memory usage for abnormal growth and set alerts to detect early signs of exhaustion.

Generated by OpenCVE AI on September 11, 2026 at 15:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:oisf:suricata:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Oisf
Oisf suricata
Vendors & Products Oisf
Oisf suricata
Type Values Removed Values Added
Description Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to versions 7.0.16 and 8.0.5,IKEv2 parser state could grow without bounds while storing client transforms. Repeated crafted UDP traffic may cause Suricata to consume excessive memory, potentially resulting in denial of service. Versions 7.0.16 and 8.0.5 fix the issue. Some workarounds are available. Disable IKE application-layer parsing if it is not needed. Alternatively, use a rule to bypass ike flows after the first packets like `alert ike any any -> any any (sid: 2; flow.pkts_toserver: > 256; bypass; noalert;)`.
Title ikev2: unbounded client transform storage can lead to resource exhaustion
Weaknesses CWE-400
CWE-770
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 11, 2026, 3:55 PM
Reserved
May 13, 2026, 7:45 AM
Status
Analyzed
Published
Sep 10, 2026, 10:16 PM
Modified
Sep 16, 2026, 6:28 PM
Severity
Important
Public date
Sep 10, 2026, 9:38 PM