dbcve.org
SuricataApplication · Oisf

CVE-2025-64333

HIGH · 7.5 CVSS v3.1 Published 2025-11-26
Fix available
A fix is available. Upgrade to 7.0.13 / 8.0.2 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 developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, a large HTTP content type, when logged can cause a stack overflow crashing Suricata. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves limiting stream.reassembly.depth to less then half the stack size. Increasing the process stack size makes it less likely the bug will trigger.

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 confidence

In Suricata versions prior to 7.0.13 and 8.0.2, a stack overflow vulnerability exists where a large HTTP content type, when processed and logged by the engine, exhausts the stack space and crashes the application. This is a denial-of-service vulnerability exploitable via crafted network traffic.

MitigationUpgrade Suricata to version 7.0.13 or 8.0.2. Alternatively, limit stream.reassembly.depth to less than half the stack size or increase the process stack size as a workaround.

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.13>= 8.0.0, < 8.0.2

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 Suricata installation and version
    Run 'suricata --version' or check package manager (dpkg -l suricata, rpm -qi suricata)
    Affected if Version is less than 7.0.13 OR between 8.0.0 and 8.0.2 (exclusive of 8.0.2)
  2. Verify HTTP logging is enabled
    Check suricata.yaml for 'outputs' section; look for 'http-log' or 'alerts' with 'http' enabled under 'app-layer.protocols.http'; also confirm 'app-layer.protocols.http: enabled' is set
    Affected if HTTP protocol and HTTP logging are both enabled (vulnerability triggers when HTTP content type is logged)
  3. Check stream.reassembly.depth setting
    In suricata.yaml, locate 'stream.reassembly.depth' under stream configuration; if not set, default is often 10000+ bytes
    Affected if stream.reassembly.depth is set to a high value (especially near or above half the stack size, default often enables the condition)
  4. Confirm the engine is processing HTTP traffic
    Review suricata.yaml for 'pcap' or 'af-packet'/'-i' interface configuration that captures live traffic, or check for pcap file processing in rules/inputs
    Affected if Suricata is actively processing network traffic (vulnerability requires incoming crafted HTTP traffic)

User is affected if running Suricata version 7.0.13 or later, or 8.0.2 or later, AND HTTP logging is enabled, AND the system processes HTTP traffic with default or high stream.reassembly.depth settings.

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.13 / 8.0.2 or later
Fixed in 7.0.138.0.2
Interim mitigation

Upgrade Suricata to version 7.0.13 or 8.0.2. Alternatively, limit stream.reassembly.depth to less than half the stack size or increase the process stack size as a workaround.

Recommended fix High confidence

Suricata 7.0.13 or 8.0.2

  1. Upgrade Suricata to version 7.0.13 or 8.0.2 (both contain the security fix)
  2. If immediate upgrade is not possible, add or modify the Suricata configuration file (suricata.yaml) to set stream.reassembly.depth to a value less than half the stack size (e.g., 4096 or lower)
  3. Alternatively, increase the process stack size at the system level (e.g., ulimit -s 16384) before starting Suricata as a mitigation
  4. After applying the fix or workaround, restart the Suricata service and verify normal operation

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

Fix this in Suricata Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64333 — 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-2025-64333 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