cve.bz

CVE-2026-45769 oisf suricata: Uncontrolled Resource Consumption

7.5 highEPSS 1.8%

High (7.5) in oisf suricata. EPSS 1.8% estimated probability of exploitation activity in the next 30 days.

On this page
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;)`.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
1.8% (unchanged from 1.8% a week ago; 1.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 79th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-09-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-45769 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-45769?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-45769?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-45769 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
oisf:suricatafrom 7.0.0 before 7.0.16
oisf:suricatafrom 8.0.0 before 8.0.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13suricatano fix listedDEBIAN-CVE-2026-45769
Debian14suricata1:8.0.5-1DEBIAN-CVE-2026-45769
Ubuntu16.04:LTS, 18.04:LTS, 22.04:LTS and 2 moresuricatano fix listedUBUNTU-CVE-2026-45769
openSUSETumbleweedsuricata8.0.5-1.1openSUSE-SU-2026:10885-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

The vulnerability in Suricata, rated as Important, allows a remote attacker to cause a denial of service by sending specially crafted UDP traffic. This can lead to unbounded memory growth within the IKEv2 parser, consuming excessive resources and potentially crashing the Suricata engine. This impact is significant in environments where Suricata is deployed for network intrusion detection or prevention.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-45769.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON