CVE-2026-22262 — Suricata: stack overflow in dataset saving (CVE-2026-22262)
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 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.5% (30-day exploitation probability)+7
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Oisf Suricata).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.9 | CVSS 3.1 | Medium | 2.2 | 3.6 | security-advisories@github.com via NIST National Vulnerability Database |
| 5.9 | CVSS 3.1 | Medium | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.55%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Analysis and videos
CVE-2026-22262: Suricata: stack overflow in dataset saving
Suricata, a network IDS, IPS and NSM engine, is affected by CVE-2026-22262, a stack overflow in the code that saves datasets when the data is too large. The record lists versions earlier than 7.0.14 and versions from 8.0.0 up to but not including 8.0.3 as affected. Patched versions are 8.0.3 and 7.0.14, and a workaround is to avoid rules that use the dataset save or state options.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · oisf/suricata
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- github.com/OISF/suricata/security/advisories/GHSA-9qg5-2gwh-xp86
- github.com/OISF/suricata/commit/32609e6896f9079c175665a94005417cec7637eb
- github.com/OISF/suricata/commit/d6bc718e303ecbec5999066b8bc88eeeca743658
- github.com/OISF/suricata/commit/27a2180bceaa3477419c78c54fce364398d011f1
- github.com/OISF/suricata/commit/32a1b9ae6aa80a60c073897e38a2ac6ea0f64521
- github.com/OISF/suricata/commit/0eff24213763c2aa2bb0957901d5dc1e18414dbf
- github.com/OISF/suricata/commit/d767dfadcd166f82683757818b9e46943326ac90
- redmine.openinfosecfoundation.org/issues/8110
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-45770 Suricata is a network Intrusion Detection System, Intrusion Prevention System and… Sep 10, 2026
- Medium CVE-2026-45767 Path Traversal in Oisf Suricata Sep 10, 2026
- High CVE-2026-45765 Uncontrolled Resource Consumption in Oisf Suricata Sep 10, 2026
- High CVE-2026-45766 Uncontrolled Resource Consumption in Oisf Suricata Sep 10, 2026
- Critical CVE-2026-45764 Type Confusion in Oisf Suricata Sep 10, 2026
- High CVE-2026-45762 Type Confusion in Oisf Suricata Sep 10, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-22262 is "Suricata: stack overflow in dataset saving (CVE-2026-22262)", rated Critical. It affects Suricata (Oisf); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 0.55% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.