CVE-2026-102281 · GHSA-m8vh-jmq9-5rjg
Nest: Remote process termination via a deeply nested microservice message pattern
- Risk score
- 66/100
- CVSS
- 7.5 v3.1
- Exploit chance (30 days)
- 0.4%
- Published
- 28 Sep 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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-s…
- Affected
- @nestjs/microservices (npm) < 11.2.4; @nestjs/microservices (npm) >= 12.0.0, < 12.0.2
- Fix
- Upgrade @nestjs/microservices to 11.2.4 or 12.0.2 (whichever matches your release line) or later.
- Exploitation
- Public proof of concept
Story map
At a glance
@nestjs/microservices: Amber, patch this week. 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-s…
The flaws
- CVE-2026-102281: Nest: Remote process termination via a deeply nested microservice message pattern (CVSS 7.5 · EPSS 0%)
- GHSA-96h4-vgxj-gvm2: Nest: Unbounded memory growth in the NestJS TCP microservice transport (CVSS 6.5)
The fix
Upgrade @nestjs/microservices: 11.2.4 · 12.0.2 or later on your release line
Who is exposed: @nestjs/microservices (npm) < 11.2.4; @nestjs/microservices (npm) >= 12.0.0, < 12.0.2
Where it stands
- Public proof of concept
Connects to
- Same weakness: CWE-248 (CWE-248). 63 other warnings in 30 days
Why it is Amber
- CVSS 7.5 high
- Public exploit or proof of concept referenced
- Remotely exploitable without logging in
- On your watchlist: npm
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| @nestjs/microservices | npm | < 11.2.4 | 11.2.4 |
| @nestjs/microservices | npm | >= 12.0.0, < 12.0.2 | 12.0.2 |
References
- https://github.com/advisories/GHSA-m8vh-jmq9-5rjg
- https://github.com/nestjs/nest/security/advisories/GHSA-m8vh-jmq9-5rjg
- https://nvd.nist.gov/vuln/detail/CVE-2026-102281
- https://github.com/nestjs/nest/pull/17737
- https://github.com/nestjs/nest/commit/aa97b5144d8dff1ce700aac521eb86449a679d6f
- https://github.com/nestjs/nest/commit/e9dcd4c7ac64361fbfe79461da85f5b3fc3e02da
- https://github.com/nestjs/nest/releases/tag/v11.2.4
- https://github.com/nestjs/nest/releases/tag/v12.0.2
- https://github.com/advisories/GHSA-m8vh-jmq9-5rjg
Original 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.
Last activity 28 Sep 2026. Patch Forecast updates every hour.