CVE-2026-31935
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSuricata is a network IDS, IPS and NSM engine. Prior to versions 7.0.15 and 8.0.4, flooding of craft HTTP2 continuation frames can lead to memory exhaustion, usually resulting in the Suricata process being shut down by the operating system. This issue has been patched in versions 7.0.15 and 8.0.4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSuricata versions prior to 7.0.15 and 8.0.4 are vulnerable to memory exhaustion via crafted HTTP2 continuation frames. An attacker can flood the engine with these frames, causing memory to fill up until the operating system terminates the Suricata process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.0.15>= 8.0.0, < 8.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Suricata installation and versionRun 'suricata --version' or 'suricata -V' to display the installed version numberAffected if Version is below 7.0.15 OR version is 8.0.0, 8.0.1, 8.0.2, or 8.0.3 (these are the affected versions)
-
Verify HTTP2 protocol detection is enabledInspect the Suricata configuration file (typically /etc/suricata/suricata.yaml) and look for 'http2' under the 'app-layer' protocols section, or check if 'http2' is listed in enabled protocolsAffected if HTTP2 protocol detection is enabled (the vulnerability only applies when Suricata is parsing HTTP2 traffic)
-
Confirm Suricata is processing HTTP trafficCheck active Suricata interfaces and rules by reviewing /etc/suricata/suricata.yaml for 'http' or 'http2' rule classifications, or run 'suricatactl stats' to see if HTTP2 counters are incrementingAffected if Suricata is actively processing HTTP2 traffic (the attack requires HTTP2 frames to reach the engine)
You are affected if Suricata version is below 7.0.15 or between 8.0.0 and 8.0.3 AND HTTP2 protocol detection is enabled and processing traffic.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.0.158.0.4
Upgrade Suricata to version 7.0.15 or 8.0.4 or later to patch this vulnerability.
7.0.15 (for 7.x branch) or 8.0.4 (for 8.x branch)
- 1. Determine current Suricata version by running 'suricata --version'
- 2. If version is < 7.0.15 and on the 7.x branch, plan upgrade to 7.0.15
- 3. If version is >= 8.0.0 and < 8.0.4 and on the 8.x branch, plan upgrade to 8.0.4
- 4. Backup existing Suricata configuration files (typically in /etc/suricata/)
- 5. Upgrade Suricata using your package manager or by compiling from source
- 6. Verify the installed version matches the target fixed release (7.0.15 or 8.0.4)
- 7. Restart the Suricata service
- 8. Monitor for normal operation and verify the memory exhaustion issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31935 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31935 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data