Response truncation via premature dump completion
Published Sep 4, 2026 · Updated Sep 4, 2026
Improper response handling in Node.js Undici 7.1.0 through 7.29.0 and 8.0.0 through 8.10.1 allows remote attackers to truncate data. The dump interceptor signals completion at maxSize for a chunked response without Content-Length but neither pauses the parser nor aborts the request. Continued body delivery triggers a second completion assertion and disconnects the connection, while the application observes a successful status with an empty or truncated body.
Summary
What happened
Improper response handling in Node.js Undici 7.1.0 through 7.29.0 and 8.0.0 through 8.10.1 allows remote attackers to truncate data. The dump interceptor signals completion at maxSize for a chunked response without Content-Length but neither pauses the parser nor aborts the request. Continued body delivery triggers a second completion assertion and disconnects the connection, while the application observes a successful status with an empty or truncated body.
The record
- CVE
- CVE-2026-84947
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- Node.js
- Product
- Undici
- Classifications
- CWE-20, CWE-248, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 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=7.1.0 <7.29.1
- Affected versionversion=8.0.0 <8.10.2
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