Memory exhaustion via ignored Web Stream backpressure
Published Feb 3, 2026 · Updated Feb 3, 2026
Denial of service in Fastify before 5.7.3 allows remote attackers to crash Node.js servers through slow Web Stream responses. sendWebStream ignored a false return from res.write() and continued reading chunks instead of waiting for the response drain event, causing unbounded buffering. The application must send a ReadableStream or a Response with a Web Stream body through reply.send(); a slow or non-reading client can then exhaust process memory.
Summary
What happened
Denial of service in Fastify before 5.7.3 allows remote attackers to crash Node.js servers through slow Web Stream responses. sendWebStream ignored a false return from res.write() and continued reading chunks instead of waiting for the response drain event, causing unbounded buffering. The application must send a ReadableStream or a Response with a Web Stream body through reply.send(); a slow or non-reading client can then exhaust process memory.
The record
- CVE
- CVE-2026-25224
- Published
- Feb 3, 2026
- Updated
- Feb 3, 2026
- Vendor
- Fastify
- Product
- Fastify
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 3, 2026CVE publishedPublication date reported by the CVE source.
- Feb 3, 2026Record 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=< 5.7.3
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