Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-22262 is a medium-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Oisf Suricata. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-22262 is a stack buffer overflow vulnerability in Suricata, an open-source network intrusion detection system (IDS), intrusion prevention system (IPS), and network security monitoring (NSM) engine. The flaw arises during dataset saving operations, where a fixed-size stack buffer prepares the data; oversized dataset content prior to versions 8.0.3 and 7.0.14 triggers the overflow. Published on 2026-01-27, it is rated 5.9 on the CVSS v3.1 scale (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) and maps to CWE-121 (Stack-based Buffer Overflow) and CWE-787 (Out-of-bounds Write).
An unauthenticated remote attacker with network access can exploit the vulnerability by crafting traffic that activates Suricata rules using oversized datasets, though this requires high attack complexity with no user interaction needed. Exploitation leads to a denial-of-service condition via stack overflow-induced application crash, disrupting IDS/IPS/NSM functionality without impacting confidentiality or integrity.
Patches resolving the issue are included in Suricata versions 8.0.3 and 7.0.14, with fixes detailed in GitHub commits from the OISF/suricata repository, such as 0eff24213763c2aa2bb0957901d5dc1e18414dbf, 27a2180bceaa3477419c78c54fce364398d011f1, 32609e6896f9079c175665a94005417cec7637eb, 32a1b9ae6aa80a60c073897e38a2ac6ea0f64521, and d6bc718e303ecbec5999066b8bc88eeeca743658. As a workaround, refrain from using rules with dataset `save` or `state` options.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-4772
Vulnerability Data
Suricata is a network IDS, IPS and NSM engine. While saving a dataset a stack buffer is used to prepare the data. Prior to versions 8.0.3 and 7.0.14, if the data in the dataset is too large, this can result…
more
in a stack overflow. Versions 8.0.3 and 7.0.14 contain a patch. As a workaround, do not use rules with datasets `save` nor `state` options.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis can discover stack-buffer overflows before deployment.
Input validation directly stops untrusted data from exceeding stack buffer bounds.
Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Secure-engineering principles include bounds-checked coding and safe buffer handling that avoid introducing the flaw.
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.
Secure-development practices directly prevent introduction of stack buffer overflows.
Vulnerability scanning can discover stack buffer overflows but does not prevent their introduction.
Patching eliminates known instances of the weakness after discovery.
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.
Security testing (fuzzing, static analysis) detects stack overflows before release.
Secure SDLC mandates buffer-safety practices that directly prevent stack overflows.
Application security requirements can specify buffer-size and input-validation rules.
Secure architecture principles include memory-safety and least-privilege stack usage.
Secure coding standards explicitly forbid unsafe buffer handling that causes CWE-121.
Change management can enforce review gates that catch unsafe memory operations before deployment.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248594 OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. prevents CWE-121
Oracle Linux 9 (1 rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-121