BaseFortify

Publication date: 2025-11-26

Last updated on: 2025-12-05

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-11-26

Last Modified

2025-12-05

Generated

2026-07-06

AI Q&A

2025-11-27

EPSS Evaluated

2026-07-05

NVD

CVE-2025-64333

Affected Vendors & Products

Vendor	Product	Version / Range
oisf	suricata	to 7.0.13 (exc)
oisf	suricata	From 8.0.0 (inc) to 8.0.2 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-121	A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Executive Summary

This vulnerability in Suricata, a network IDS/IPS/NSM engine, occurs when logging a large HTTP content type, which can cause a stack overflow and crash the Suricata process. It affects versions prior to 7.0.13 and 8.0.2 and has been patched in those versions.

Impact Analysis

The vulnerability can cause Suricata to crash due to a stack overflow when processing large HTTP content types. This can lead to denial of service, reducing the effectiveness of network intrusion detection and prevention, potentially leaving the network unmonitored or unprotected during the crash.

Mitigation Strategies

To mitigate this vulnerability, update Suricata to version 7.0.13 or 8.0.2 or later where the issue is patched. As a workaround, limit the stream.reassembly.depth setting to less than half the process stack size. Additionally, increasing the process stack size can reduce the likelihood of the bug triggering.

Hi! I’m here to help you understand CVE-2025-64333. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70