CVE-2025-53538

7.5

OISF (Open Information Security Foundation) · Suricata

A vulnerability in Suricata allows unauthenticated attackers to cause uncontrolled memory usage via crafted HTTP/2 stream 0 data, resulting in a potential loss of network security monitoring visibility.

Executive summary

Suricata is susceptible to an uncontrolled resource consumption vulnerability that can lead to a denial of service by exhausting system memory during HTTP/2 traffic processing.

Vulnerability

This flaw involves the improper handling of data on HTTP/2 stream 0, which triggers uncontrolled memory allocation (CWE-770/CWE-400). The attack vector is network-based and requires no authentication or user interaction to exploit.

Business impact

Successful exploitation of this vulnerability results in a denial of service for the network security monitoring infrastructure. Because Suricata functions as an IDS/IPS, a crash or memory exhaustion event directly compromises the security posture of the organization by creating a blind spot in traffic inspection, potentially allowing malicious activity to pass undetected. The CVSS score of 7.5 reflects the high availability impact this flaw poses to critical security infrastructure.

Remediation

Immediate Action: Update Suricata to version 7.0.11 or 8.0.0 as soon as possible to incorporate the necessary resource management patches.

Proactive Monitoring: Monitor system memory usage and Suricata process stability for unexpected spikes or service restarts that may indicate attempted exploitation.

Compensating Controls: If immediate patching is not feasible, disable the HTTP/2 parser or implement the recommended Suricata signature to drop malicious HTTP/2 frame types targeting stream 0.

Exploitation status

Public Exploit Available: No (exploit_available: unknown)

Analyst recommendation

Given that Suricata is a foundational component of network defense, this vulnerability presents a significant risk to overall visibility. Security teams should prioritize the deployment of the vendor-provided patches. If patching must be delayed, the provided detection and mitigation signatures should be applied immediately to neutralize the threat vector while maintaining operational continuity.

Sources