Resource retention via canceled StreamableFile responses
Published Mar 6, 2023 · Updated Mar 5, 2025
Resource leak in NestJS @nestjs/core before 9.0.5 allows remote attackers to retain StreamableFile backing streams by canceling requests. ExpressAdapter passes the source stream to stream.pipe(response), which does not destroy that source when the HTTP response closes or errors. Reachability requires an Express application endpoint returning StreamableFile; pooled upstream streams can retain sockets and leave dependent requests hanging.
Summary
What happened
Resource leak in NestJS @nestjs/core before 9.0.5 allows remote attackers to retain StreamableFile backing streams by canceling requests. ExpressAdapter passes the source stream to stream.pipe(response), which does not destroy that source when the HTTP response closes or errors. Reachability requires an Express application endpoint returning StreamableFile; pooled upstream streams can retain sockets and leave dependent requests hanging.
The record
- CVE
- CVE-2023-26108
- Published
- Mar 6, 2023
- Updated
- Mar 5, 2025
- Vendor
- NestJS
- Product
- @nestjs/core
- Classifications
- CWE-200, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2023CVE publishedPublication date reported by the CVE source.
- Mar 5, 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=0 <9.0.5
What conditions does exploitation require?
What is affected?
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