[ CVE-2026-102281 · Published 28 Sep 2026 ]
Nest: Remote process termination via a deeply nested microservice message pattern
[ Why it matters ]Priority signals
- Public proof-of-concept exploit exists (CISA SSVC)
[ Description ]Official description
Nest is a framework for building scalable Node.js server-side applications. Prior to 11.2.4 and 12.0.2, a single message with a deeply nested object in its pattern can terminate a NestJS microservice using the TCP or RabbitMQ transport. ServerTCP#handleMessage and ServerRMQ#handleMessage pass a client-controlled non-string pattern to JSON.stringify to derive the handler lookup key; sufficiently deep nesting throws RangeError: Maximum call stack size exceeded, and the unhandled promise rejection terminates Node.js under its default behavior. An attacker who can reach the TCP port or publish to the consumed RabbitMQ queue or exchange can crash the service on demand; other transports are not affected because their patterns arrive as strings. This issue is fixed in versions 11.2.4 and 12.0.2.
[ Fixes ]Fixes and patches
- @nestjs/microservices 11.2.4Fixed version · GitHub Advisories · npm package @nestjs/microservices: upgrade to 11.2.4 or later (affected < 11.2.4)
- @nestjs/microservices 12.0.2Fixed version · GitHub Advisories · npm package @nestjs/microservices: upgrade to 12.0.2 or later (affected >= 12.0.0, < 12.0.2)
[ Packages ]Affected open-source packages
- @nestjs/microservices npmAffected < 11.2.4 · fixed in 11.2.4 · GHSA-m8vh-jmq9-5rjg
- @nestjs/microservices npmAffected >= 12.0.0, < 12.0.2 · fixed in 12.0.2 · GHSA-m8vh-jmq9-5rjg
[ References ]References
- github.com/nestjs/nest/commit/aa97b5144d8dff1ce700aac521eb86449a679d6f
- github.com/nestjs/nest/commit/e9dcd4c7ac64361fbfe79461da85f5b3fc3e02da
- github.com/nestjs/nest/pull/17737
- github.com/nestjs/nest/releases/tag/v11.2.4
- github.com/nestjs/nest/releases/tag/v12.0.2
- github.com/nestjs/nest/security/advisories/GHSA-m8vh-jmq9-5rjg