dbcve.org
SuricataApplication · Oisf

CVE-2026-31933

HIGH · 7.5 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to 7.0.15 / 8.0.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Suricata is a network IDS, IPS and NSM engine. Prior to versions 7.0.15 and 8.0.4, specially crafted traffic can cause Suricata to slow down, affecting performance in IDS mode. 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 · moderate confidence

Suricata network IDS/IPS engine prior to versions 7.0.15 and 8.0.4 contains a denial-of-service vulnerability where specially crafted network traffic causes significant performance degradation (slowdown) specifically in IDS detection mode, allowing attackers to degrade IDS monitoring capabilities.

MitigationUpgrade Suricata to version 7.0.15 or 8.0.4 or later to patch the vulnerability; in the interim, consider network segmentation to limit exposure to untrusted traffic sources.

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
SuricataApplication
Affected:< 7.0.15>= 8.0.0, < 8.0.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Suricata version
    Run 'suricata --version' or check the package manager (dpkg -l suricata, rpm -qi suricata) to determine the exact version number
    Affected if The version is less than 7.0.15, or greater than or equal to 8.0.0 but less than 8.0.4
  2. Confirm Suricata is running in IDS detection mode
    Inspect the suricata.yaml configuration file and verify the runmode is set to 'autofp' or 'workers' (IDS modes) rather than 'inline' or 'nfq' (IPS modes). Also check if the -i flag (interface mode) is used rather than --inline in the startup command
    Affected if Suricata is configured in IDS detection mode (passive monitoring) rather than inline IPS mode; the vulnerability specifically affects IDS mode only
  3. Verify network exposure to untrusted traffic
    Check which network interfaces Suricata is monitoring (ps aux | grep suricata, or look at 'af-packet' or 'pcap' configuration sections in suricata.yaml). Determine if these interfaces receive traffic from untrusted or external networks
    Affected if The monitored interfaces process traffic from untrusted or attacker-controlled network sources, as the vulnerability is triggered by specially crafted network packets

You are affected if your Suricata version is below 7.0.15 or between 8.0.0 and 8.0.4 AND the system is running in IDS detection mode processing potentially malicious network traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.0.15 / 8.0.4 or later
Fixed in 7.0.158.0.4
Interim mitigation

Upgrade Suricata to version 7.0.15 or 8.0.4 or later to patch the vulnerability; in the interim, consider network segmentation to limit exposure to untrusted traffic sources.

Recommended fix High confidence

7.0.15 (for 7.x branch) or 8.0.4 (for 8.x branch)

  1. 1. Check current Suricata version using 'suricata --version'
  2. 2. If version is < 7.0.15 or >= 8.0.0 but < 8.0.4, plan for upgrade
  3. 3. For Suricata 7.x users: upgrade to version 7.0.15
  4. 4. For Suricata 8.x users: upgrade to version 8.0.4
  5. 5. Verify the upgrade was successful by running 'suricata --version' again
  6. 6. Restart the Suricata service to load the patched version
Caveat Review release notes for any configuration or rule syntax changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Suricata Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31933 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31933 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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