Visibility loss via stream-zero file-state retention
Published Jul 22, 2025 · Updated Jul 23, 2025
Resource exhaustion in Suricata before 7.0.11 and 8.0.0-beta1 through 8.0.0-rc1 allows remote attackers to disrupt monitoring. The HTTP/2 parser marks the global stream-zero transaction as able to hold files; DATA frames then open file state that completed transactions never close. No authentication or user interaction is required, and sustained crafted traffic grows memory until network-monitoring visibility is lost.
Summary
What happened
Resource exhaustion in Suricata before 7.0.11 and 8.0.0-beta1 through 8.0.0-rc1 allows remote attackers to disrupt monitoring. The HTTP/2 parser marks the global stream-zero transaction as able to hold files; DATA frames then open file state that completed transactions never close. No authentication or user interaction is required, and sustained crafted traffic grows memory until network-monitoring visibility is lost.
The record
- CVE
- CVE-2025-53538
- Published
- Jul 22, 2025
- Updated
- Jul 23, 2025
- Vendor
- Open Information Security Foundation
- Product
- Suricata
- Classifications
- CWE-770, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2025CVE publishedPublication date reported by the CVE source.
- Jul 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.0.11
- Affected versionversion=>= 8.0.0-beta1, < 8.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo