Nest: Unbounded memory growth in the NestJS TCP microservice transport — GHSA-96H4-VGXJ-GVM2

Summary

## Summary A peer that can open a TCP connection to a NestJS microservice using the built-in TCP transport can make the server process allocate memory without limit, on either side of the connection, until the process is killed by the OS or by its container memory limit. No authentication, no credentials, and no valid message are required. Applications are affected only if they start a microservice with…

Timeline

Published by source

2026-09-30

Risk context

• Reported severity or threat level: medium.
• Reported CVSS score: 6.5 out of 10.
• Review exposure for the affected product or family: npm: @nestjs/microservices.

Product

npm: @nestjs/microservices

What to do

General, cautious steps (verify details in the official source):

• Review exposure and plan remediation based on risk and environment.
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source

Evidence and provenance

Canonical advisory ID

GHSA-96H4-VGXJ-GVM2

Source

GitHub

Vendor

GitHub

Published by source

2026-09-30

Last source activity

2026-09-30

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.