dbcve.org
SuricataApplication · Oisf

CVE-2025-64331

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 stack overflow can occur on large HTTP file transfers if the user has increased the HTTP response body limit and enabled the logging of printable http bodies. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves using default HTTP response body limits and/or disabling http-body-printable logging; body logging is disabled by default.

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

A stack overflow vulnerability exists in Suricata versions prior to 7.0.13 and 8.0.2 when processing large HTTP file transfers. The overflow occurs specifically when a user has increased the HTTP response body limit AND enabled logging of printable HTTP bodies (http-body-printable), allowing potential denial of service or possible code execution.

MitigationUpgrade to Suricata version 7.0.13 or 8.0.2, or alternatively use default HTTP response body limits and/or disable http-body-printable logging (which is disabled by default).

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. Check Suricata version
    Run `suricata --version` and note the version number displayed
    Affected if Version is below 7.0.13, or is 8.0.0 or 8.0.1 (versions prior to 8.0.2)
  2. Locate Suricata configuration file
    Find the suricata.yaml configuration file, typically in /etc/suricata/ or the directory where Suricata is installed
    Affected if Configuration file exists and is in use by your deployment
  3. Verify http-body-printable logging is enabled
    Search the configuration file for `http-body-printable` and confirm it is set to `true` or `yes`
    Affected if http-body-printable is explicitly enabled (not set to false or absent)
  4. Check HTTP response body limit setting
    Search the configuration file for `http.response-body-limit` or similar and note the configured value
    Affected if The response body limit is set to a value higher than the default (which is typically around 10MB or less)

You are affected if your Suricata version is less than 7.0.13 or between 8.0.0 and 8.0.1 AND you have both http-body-printable enabled AND a non-default increased HTTP response body limit configured.

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 to Suricata version 7.0.13 or 8.0.2, or alternatively use default HTTP response body limits and/or disable http-body-printable logging (which is disabled by default).

Recommended fix High confidence

Upgrade to Suricata 7.0.13 (for 7.x users) or 8.0.2 (for 8.x users)

  1. 1. Check current Suricata version using 'suricata --version'
  2. 2. For Suricata 7.x users: upgrade to version 7.0.13 or later
  3. 3. For Suricata 8.x users: upgrade to version 8.0.2 or later
  4. 4. After upgrade, verify the version again with 'suricata --version'
  5. 5. Review and test your Suricata configuration to ensure all rules and settings work as expected
  6. 6. (Optional workaround only if upgrade not possible) Ensure HTTP response body limits are at default values and verify http-body-printable logging is disabled in suricata.yaml

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
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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