Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-71418 is a high-severity Inefficient Algorithmic Complexity (CWE-407) vulnerability in Openinfosecfoundation (inferred from references). Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-83397
Vulnerability Data
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. From 8.0.0 until 8.0.6, DNS-over-HTTP/2 processing in rust/src/http2/http2.rs retains previously processed HTTP/2 DATA frame contents instead of clearing the internal buffer. Multiple DATA frames with…
more
the EndOfStream flag set can grow the buffer to its 65 KiB limit while causing all prior contents to be processed again, producing quadratic CPU complexity, degraded packet processing, loss of monitoring visibility, or denial of service. This issue is fixed in version 8.0.6.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.9
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Addresses inefficient algorithms whose complexity can be exploited for DoS.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Runtime monitoring of software and resources can detect the performance impact of triggered worst-case complexity.
Identifying and recording algorithmic-complexity vulnerabilities directly addresses the root cause before exploitation.
Secure SDLC practices (code review, complexity analysis, safe algorithm selection) prevent introduction of exploitable worst-case behavior.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Redundancy of processing facilities can absorb resource exhaustion from inefficient algorithms.
Monitoring activities can identify anomalous resource consumption indicative of algorithmic complexity attacks.
Secure development life cycle includes design reviews that can catch inefficient algorithms before deployment.
Secure system architecture principles encourage selection of algorithms with acceptable worst-case complexity.
Secure coding practices can include guidelines to avoid or mitigate inefficient algorithms.
Security testing can uncover performance issues stemming from algorithmic complexity.