VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@nestjs/microservices: vulnerability history, versions and safety

@nestjs/microservices is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 99 releases, from Apr 2026 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 30 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @nestjs/microservices vulnerabilities

Vulert verdict on @nestjs/microservices 12.2.0 i

Updated on 23 Oct 2026

Good news: 12.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 12.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 12.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 12.2.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 30 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 73 packages i
  • Stars 76,853 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @nestjs/microservices, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
12.2.0 19 Oct 2026 none MIT — Details →
12.1.3 12 Oct 2026 none MIT — Details →
11.2.7 30 Sep 2026 none MIT — Details →
12.1.2 30 Sep 2026 none MIT — Details →
12.1.1 28 Sep 2026 none MIT — Details →
11.2.6 23 Sep 2026 none MIT — Details →
12.1.0 23 Sep 2026 none MIT — Details →
12.0.4 21 Sep 2026 none MIT — Details →
12.0.3 15 Sep 2026 none MIT — Details →
11.2.5 15 Sep 2026 none MIT — Details →
11.2.4 14 Sep 2026 M1 MIT Yes Details →
12.0.2 14 Sep 2026 none MIT — Details →
12.0.1 27 Aug 2026 none MIT — Details →
12.0.0 27 Aug 2026 none MIT — Details →
12.0.0-alpha.7 26 Aug 2026 none MIT — Details →
11.2.3 25 Aug 2026 H1 M1 MIT Yes Details →
11.2.2 25 Aug 2026 H1 M1 MIT Yes Details →
12.0.0-alpha.6 24 Aug 2026 none MIT — Details →
11.2.1 14 Aug 2026 H1 M1 MIT Yes Details →
11.2.0 14 Aug 2026 H1 M1 MIT Yes Details →
11.1.29 10 Aug 2026 H1 M1 MIT Yes Details →
11.1.28 08 Jul 2026 H1 M1 MIT Yes Details →
11.1.27 15 Jun 2026 H1 M1 MIT Yes Details →
11.1.26 08 Jun 2026 H1 M1 MIT Yes Details →
11.1.25 08 Jun 2026 H1 M1 MIT Yes Details →
12.0.0-alpha.5 25 May 2026 none MIT — Details →
11.1.24 25 May 2026 H1 M1 MIT Yes Details →
11.1.23 21 May 2026 H1 M1 MIT Yes Details →
11.1.22 21 May 2026 H1 M1 MIT Yes Details →
12.0.0-alpha.4 14 May 2026 none MIT — Details →
12.0.0-alpha.3 14 May 2026 none MIT — Details →
11.1.21 14 May 2026 H1 M1 MIT Yes Details →
11.1.20 13 May 2026 H1 M1 MIT Yes Details →
11.1.19 13 Apr 2026 H1 M1 MIT Yes Details →
11.1.18 03 Apr 2026 H2 M1 MIT Yes Details →
11.1.17 16 Mar 2026 H2 M1 MIT Yes Details →
12.0.0-alpha.2 10 Mar 2026 none MIT — Details →
12.0.0-alpha.1 05 Mar 2026 none MIT — Details →
12.0.0-alpha.0 05 Mar 2026 none MIT — Details →
11.1.16 05 Mar 2026 H2 M1 MIT Yes Details →
11.1.15 03 Mar 2026 H2 M1 MIT Yes Details →
11.1.14 17 Feb 2026 H2 M1 MIT Yes Details →
11.1.13 03 Feb 2026 H2 M1 MIT Yes Details →
11.1.12 15 Jan 2026 H2 M1 MIT Yes Details →
10.4.22 10 Jan 2026 H2 M1 MIT Yes Details →
10.4.21 08 Jan 2026 H2 M1 MIT Yes Details →
11.1.11 29 Dec 2025 H2 M1 MIT Yes Details →
11.1.10 22 Dec 2025 H2 M1 MIT Yes Details →
11.1.9 14 Nov 2025 H2 M1 MIT Yes Details →
11.1.8 27 Oct 2025 H2 M1 MIT Yes Details →
11.1.7 21 Oct 2025 H2 M1 MIT Yes Details →
11.1.6 07 Aug 2025 H2 M1 MIT Yes Details →
10.4.20 23 Jul 2025 H2 M1 MIT Yes Details →
11.1.5 18 Jul 2025 H2 M1 MIT Yes Details →
11.1.4 16 Jul 2025 H2 M1 MIT Yes Details →
10.4.19 09 Jun 2025 H2 M1 MIT Yes Details →
11.1.3 06 Jun 2025 H2 M1 MIT Yes Details →
10.4.18 26 May 2025 H2 M1 MIT Yes Details →
11.1.2 26 May 2025 H2 M1 MIT Yes Details →
11.1.1 14 May 2025 H2 M1 MIT Yes Details →
11.1.0 23 Apr 2025 H2 M1 MIT Yes Details →
11.0.21 23 Apr 2025 H2 M1 MIT Yes Details →
11.0.20 16 Apr 2025 H2 M1 MIT Yes Details →
11.0.19 15 Apr 2025 H2 M1 MIT Yes Details →
10.4.17 15 Apr 2025 H2 M1 MIT Yes Details →
11.0.18 15 Apr 2025 H2 M1 MIT Yes Details →
11.0.17 14 Apr 2025 H2 M1 MIT Yes Details →
10.4.16 14 Apr 2025 H2 M1 MIT Yes Details →
11.0.16 11 Apr 2025 H2 M1 MIT Yes Details →
11.0.15 10 Apr 2025 H2 M1 MIT Yes Details →
11.0.14 09 Apr 2025 H2 M1 MIT Yes Details →
11.0.13 03 Apr 2025 H2 M1 MIT Yes Details →
11.0.12 19 Mar 2025 H2 M1 MIT Yes Details →
11.0.11 28 Feb 2025 H2 M1 MIT Yes Details →
11.0.10 17 Feb 2025 H2 M1 MIT Yes Details →
11.0.9 10 Feb 2025 H2 M1 MIT Yes Details →
11.0.8 06 Feb 2025 H2 M1 MIT Yes Details →
11.0.7 31 Jan 2025 H2 M1 MIT Yes Details →
11.0.6 27 Jan 2025 H2 M1 MIT Yes Details →
11.0.5 23 Jan 2025 H2 M1 MIT Yes Details →
11.0.4 22 Jan 2025 H2 M1 MIT Yes Details →
11.0.3 20 Jan 2025 H2 M1 MIT Yes Details →
11.0.2 20 Jan 2025 H2 M1 MIT Yes Details →
11.0.1 16 Jan 2025 H2 M1 MIT Yes Details →
11.0.0 16 Jan 2025 H2 M1 MIT Yes Details →
10.4.15 09 Dec 2024 H2 M1 MIT Yes Details →
10.4.14 09 Dec 2024 H2 M1 MIT Yes Details →
11.0.0-next.4 05 Dec 2024 H2 M1 MIT Yes Details →
11.0.0-next.3 05 Dec 2024 H2 M1 MIT Yes Details →
10.4.13 03 Dec 2024 H2 M1 MIT Yes Details →
10.4.12 29 Nov 2024 H2 M1 MIT Yes Details →
11.0.0-next.2 28 Nov 2024 H2 M1 MIT Yes Details →
11.0.0-next.1 28 Nov 2024 H2 M1 MIT Yes Details →
10.4.11 27 Nov 2024 H2 M1 MIT Yes Details →
10.4.10 27 Nov 2024 H2 M1 MIT Yes Details →
10.4.9 25 Nov 2024 H2 M1 MIT Yes Details →
10.4.8 15 Nov 2024 H2 M1 MIT Yes Details →
10.4.7 05 Nov 2024 H2 M1 MIT Yes Details →
10.4.6 23 Oct 2024 H2 M1 MIT Yes Details →
10.4.5 16 Oct 2024 H2 M1 MIT Yes Details →
10.4.4 23 Sep 2024 H2 M1 — Yes Details →
10.4.3 17 Sep 2024 H2 M1 — Yes Details →
10.4.2 16 Sep 2024 H2 M1 — Yes Details →
10.4.1 13 Aug 2024 H2 M1 — Yes Details →
10.4.0 12 Aug 2024 H2 M1 — Yes Details →
10.3.10 01 Jul 2024 H2 M1 — Yes Details →
10.3.9 03 Jun 2024 H2 M1 — Yes Details →
10.3.8 19 Apr 2024 H2 M1 — Yes Details →
10.3.7 28 Mar 2024 H2 M1 — Yes Details →
10.3.6 27 Mar 2024 H2 M1 — Yes Details →
10.3.5 22 Mar 2024 H2 M1 — Yes Details →
10.3.4 18 Mar 2024 H2 M1 — Yes Details →
10.3.3 12 Feb 2024 H2 M1 — Yes Details →
10.3.2 07 Feb 2024 H2 M1 — Yes Details →
10.3.1 23 Jan 2024 H2 M1 — Yes Details →
10.3.0 18 Dec 2023 H2 M1 — Yes Details →
10.2.10 20 Nov 2023 H2 M1 — Yes Details →
10.2.9 17 Nov 2023 H2 M1 — Yes Details →
10.2.8 02 Nov 2023 H2 M1 — Yes Details →
10.2.7 05 Oct 2023 H2 M1 — Yes Details →

The newest 120 of 451 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @nestjs/microservices

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in @nestjs/microservices: Recursive handleData in JsonSocket 7.5 high 11.1.19 14 Apr 2026
CVE-2026-102281: @nestjs/microservices Remote Process Termination via Deeply Nested Message Pattern 7.5 high 11.2.4 29 Sep 2026
Unbounded Memory Growth in NestJS TCP Microservice Transport Vulnerability 6.5 medium 11.2.5 30 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @nestjs/microservices

Is @nestjs/microservices safe to use?

Vulert records 3 vulnerabilities for @nestjs/microservices in npm: 0 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @nestjs/microservices's Vulert package health score?

Vulert scores @nestjs/microservices 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @nestjs/microservices affected?

No. 12.2.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @nestjs/microservices have?

3 vulnerabilities are recorded for @nestjs/microservices in the npm ecosystem: 0 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @nestjs/microservices vulnerabilities disclosed?

3 vulnerabilities were recorded for @nestjs/microservices in the last 12 months, and the oldest entry in this database dates to 14 Apr 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @nestjs/microservices are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @nestjs/microservices for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @nestjs/microservices version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.