Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

Nest: Unbounded memory growth in the NestJS TCP microservice transport

GHSA-96h4-vgxj-gvm2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nestjs/microservices 12.0.3, 11.2.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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 Transport.TCP and the transport's port is reachable by an untrusted peer. Affected versions | Package | Affected | Patched | |---|---|---| | @nestjs/microservices | = 12.0.0, < 12.0.3 | 12.0.3 | | @nestjs/microservices | < 11.2.5 | 11.2.5 | The same code is present in the 10.x line and earlier. Those lines are end-of-life and will not receive a patch; upgrade to a supported major. Only @nestjs/microservices is affected. No other package needs updating for this issue. Details Two independent paths let one peer grow the heap without bound. Partial packets are buffered with nothing to reap…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-96h4-vgxj-gvm2

  2. Revision 2 · amended ·

    Amended from osv record GHSA-96h4-vgxj-gvm2

  3. Revision 1 · created ·

    Published from ghsa record GHSA-96h4-vgxj-gvm2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-96h4-vgxj-gvm2

Advisory: Nest: Unbounded memory growth in the NestJS TCP microservice transport
IDs: GHSA-96h4-vgxj-gvm2
Record: https://patchnext.com/advisories/ghsa-96h4-vgxj-gvm2 (revision 3, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @nestjs/microservices 12.0.3, 11.2.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nestjs/microservices: affected < 11.2.5; >= 12.0.0, < 12.0.3; fixed in 12.0.3, 11.2.5

## Suggested inspection (read-only)
- `npm ls @nestjs/microservices --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @nestjs/microservices.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-96h4-vgxj-gvm2 (GitHub-reviewed advisory GHSA-96h4-vgxj-gvm2 lists affected ranges: npm @nestjs/microservices >=0 =12.0.0 <12.0.3)
- Verified: https://osv.dev/vulnerability/GHSA-96h4-vgxj-gvm2 (OSV record GHSA-96h4-vgxj-gvm2 lists affected ranges: npm @nestjs/microservices >=0 =12.0.0 <12.0.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…