Unauthenticated process crash via recursive JSON handling
Published Apr 21, 2026 · Updated Apr 21, 2026
Uncontrolled recursion in NestJS Nest before 11.1.19 allows remote attackers to crash TCP microservices with bundled JSON messages. JsonSocket.handleData() recursively processes each valid JSON message while shrinking its buffer, so the configured maximum buffer size does not stop stack growth. A single approximately 47 KB TCP frame can exhaust the Node.js call stack and raise RangeError without authentication or user interaction, interrupting the affected process.
Summary
What happened
Uncontrolled recursion in NestJS Nest before 11.1.19 allows remote attackers to crash TCP microservices with bundled JSON messages. JsonSocket.handleData() recursively processes each valid JSON message while shrinking its buffer, so the configured maximum buffer size does not stop stack growth. A single approximately 47 KB TCP frame can exhaust the Node.js call stack and raise RangeError without authentication or user interaction, interrupting the affected process.
The record
- CVE
- CVE-2026-40879
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- NestJS
- Product
- Nest
- Classifications
- CWE-674, CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 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=< 11.1.19
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