VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

nats: vulnerability history, versions and safety

nats is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 5 releases, from Oct 2020 to Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nats vulnerabilities

Vulert verdict on nats 2.29.3 i

Updated on 23 Oct 2026

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

Package health score 45/100
  • Security No known security issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Moderate

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 2.29.3 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 06 Apr 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 868 packages i
  • Stars 1,602 i
  • Last release 19 months ago i
  • Licence Apache-2.0 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 nats, 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
2.29.3 19 Mar 2025 none Apache-2.0 — Details →
2.29.2 14 Feb 2025 none Apache-2.0 — Details →
2.29.1 10 Jan 2025 none Apache-2.0 — Details →
2.29.0 10 Jan 2025 none Apache-2.0 — Details →
2.28.2 30 Jul 2024 none Apache-2.0 — Details →
2.28.1 24 Jul 2024 none Apache-2.0 — Details →
2.28.0 01 Jul 2024 none Apache-2.0 — Details →
2.27.0 20 Jun 2024 none Apache-2.0 — Details →
2.26.0 20 May 2024 none Apache-2.0 — Details →
2.25.0 09 May 2024 none Apache-2.0 — Details →
2.24.0 03 May 2024 none Apache-2.0 — Details →
2.23.0 22 Apr 2024 none Apache-2.0 — Details →
2.22.0 10 Apr 2024 none Apache-2.0 — Details →
2.21.0 27 Mar 2024 none Apache-2.0 — Details →
2.20.0 12 Mar 2024 none Apache-2.0 — Details →
2.19.0 05 Dec 2023 none Apache-2.0 — Details →
2.18.0 02 Nov 2023 none Apache-2.0 — Details →
2.17.1-3 26 Oct 2023 none Apache-2.0 — Details →
2.17.1-2 17 Oct 2023 none Apache-2.0 — Details →
2.17.1-1 06 Oct 2023 none Apache-2.0 — Details →
2.17.0 21 Sep 2023 none Apache-2.0 — Details →
2.16.0 16 Aug 2023 none Apache-2.0 — Details →
2.15.1 22 Jun 2023 none Apache-2.0 — Details →
2.15.0 17 Jun 2023 none Apache-2.0 — Details →
2.15.0-2 16 Jun 2023 none Apache-2.0 — Details →
2.15.0-1 15 Jun 2023 none Apache-2.0 — Details →
2.15.0-0 15 Jun 2023 none Apache-2.0 — Details →
2.14.0 23 May 2023 none Apache-2.0 — Details →
2.14.0-2 23 May 2023 none Apache-2.0 — Details →
2.14.0-1 19 May 2023 none Apache-2.0 — Details →
2.13.1 11 Mar 2023 none Apache-2.0 — Details →
2.13.0 08 Mar 2023 none Apache-2.0 — Details →
2.12.2-1 22 Feb 2023 none Apache-2.0 — Details →
2.12.1 21 Feb 2023 none Apache-2.0 — Details →
2.12.0 09 Feb 2023 none Apache-2.0 — Details →
2.11.0 18 Jan 2023 none Apache-2.0 — Details →
2.10.3 12 Jan 2023 none Apache-2.0 — Details →
2.10.2 21 Dec 2022 none Apache-2.0 — Details →
2.10.1 20 Dec 2022 none Apache-2.0 — Details →
2.10.0 19 Dec 2022 none Apache-2.0 — Details →
2.9.2 01 Dec 2022 none Apache-2.0 — Details →
2.9.1 29 Nov 2022 none Apache-2.0 — Details →
2.9.1-0 17 Nov 2022 none Apache-2.0 — Details →
2.9.0 02 Nov 2022 none Apache-2.0 — Details →
2.8.1-2 02 Nov 2022 none Apache-2.0 — Details →
2.8.1-1 27 Oct 2022 none Apache-2.0 — Details →
2.8.1-0 25 Oct 2022 none Apache-2.0 — Details →
2.8.0 22 Aug 2022 none Apache-2.0 — Details →
2.7.1 26 May 2022 none Apache-2.0 — Details →
2.7.1-2 25 May 2022 none Apache-2.0 — Details →
2.7.1-1 25 May 2022 none Apache-2.0 — Details →
2.7.0 18 May 2022 none Apache-2.0 — Details →
2.7.0-1 23 Feb 2022 none Apache-2.0 — Details →
2.6.1 14 Feb 2022 none Apache-2.0 — Details →
2.6.0 02 Feb 2022 none Apache-2.0 — Details →
2.5.0 19 Jan 2022 none Apache-2.0 — Details →
2.5.0-3 19 Jan 2022 none Apache-2.0 — Details →
2.5.0-2 20 Dec 2021 none Apache-2.0 — Details →
2.5.0-1 02 Dec 2021 none Apache-2.0 — Details →
2.4.0 11 Nov 2021 none Apache-2.0 — Details →
2.3.1-1 04 Nov 2021 none Apache-2.0 — Details →
2.3.0 02 Nov 2021 none Apache-2.0 — Details →
2.3.0-1 02 Nov 2021 none Apache-2.0 — Details →
2.2.1-2 01 Oct 2021 none Apache-2.0 — Details →
2.2.1-1 01 Oct 2021 none Apache-2.0 — Details →
2.2.0 25 Aug 2021 none Apache-2.0 — Details →
2.1.1-1 20 Aug 2021 none Apache-2.0 — Details →
2.1.0 02 Jul 2021 none Apache-2.0 — Details →
2.0.8 24 Jun 2021 none Apache-2.0 — Details →
2.0.6 02 Jun 2021 none Apache-2.0 — Details →
2.0.4 10 May 2021 none Apache-2.0 — Details →
2.0.3-3 14 Apr 2021 none Apache-2.0 — Details →
2.0.3-2 14 Apr 2021 none Apache-2.0 — Details →
2.0.3-1 12 Apr 2021 none Apache-2.0 — Details →
2.0.2 05 Apr 2021 none Apache-2.0 — Details →
2.0.1 27 Mar 2021 none Apache-2.0 — Details →
2.0.0 15 Mar 2021 none Apache-2.0 — Details →
2.0.0-222 15 Mar 2021 none Apache-2.0 — Details →
2.0.0-220 25 Feb 2021 none Apache-2.0 — Details →
2.0.0-219 16 Feb 2021 none Apache-2.0 — Details →
2.0.0-218 08 Feb 2021 none Apache-2.0 — Details →
2.0.0-216 25 Jan 2021 none Apache-2.0 — Details →
2.0.0-215 07 Jan 2021 none Apache-2.0 — Details →
2.0.0-214 24 Dec 2020 none Apache-2.0 — Details →
2.0.0-213 17 Nov 2020 none Apache-2.0 — Details →
2.0.0-212 29 Oct 2020 none Apache-2.0 — Details →
2.0.0-211 21 Oct 2020 none Apache-2.0 — Details →
2.0.0-210 16 Oct 2020 none Apache-2.0 — Details →
2.0.0-209 29 Sep 2020 none Apache-2.0 — Details →
2.0.0-206 17 Sep 2020 C1 H1 Apache-2.0 Yes Details →
2.0.0-205 11 Sep 2020 C1 H1 Apache-2.0 Yes Details →
2.0.0-204 04 Sep 2020 C1 H1 Apache-2.0 Yes Details →
2.0.0-202 03 Sep 2020 C1 H1 Apache-2.0 Yes Details →
2.0.0-201 03 Sep 2020 C1 H1 Apache-2.0 Yes Details →
1.4.12 07 Aug 2020 none Apache-2.0 — Details →
1.4.10-0 16 Jun 2020 none Apache-2.0 — Details →
2.0.0-27 30 Apr 2020 none Apache-2.0 — Details →
1.4.9 29 Apr 2020 none Apache-2.0 — Details →
2.0.0-26 27 Apr 2020 none Apache-2.0 — Details →
2.0.0-25 23 Apr 2020 none Apache-2.0 — Details →
2.0.0-24 20 Apr 2020 none — — Details →
2.0.0-23 20 Apr 2020 none — — Details →
2.0.0-22 30 Mar 2020 none — — Details →
1.4.9-1 26 Mar 2020 none — — Details →
1.4.9-0 25 Mar 2020 none — — Details →
1.4.8 25 Mar 2020 none — — Details →
1.4.8-0 24 Mar 2020 none — — Details →
1.4.6 24 Mar 2020 none — — Details →
1.4.6-0 24 Mar 2020 none — — Details →
1.4.4 24 Mar 2020 none — — Details →
2.0.0-21 24 Mar 2020 none — — Details →
2.0.0-20 04 Mar 2020 none — — Details →
2.0.0-19 04 Mar 2020 none — — Details →
2.0.0-18 03 Mar 2020 none — — Details →
2.0.0-17 02 Mar 2020 none — — Details →
2.0.0-16 28 Feb 2020 none — — Details →
2.0.0-15 27 Feb 2020 none — — Details →
2.0.0-14 26 Feb 2020 none — — Details →
2.0.0-13 26 Feb 2020 none — — Details →
2.0.0-12 26 Feb 2020 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for nats

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-26149: Sensitive Data Exposure in NATS 7.5 high 2.0.0-209 08 Oct 2020
Information Disclosure in nats npm Package N/A critical 2.0.0-209 06 Apr 2021

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 nats

Is nats safe to use?

Vulert records 2 vulnerabilities for nats in npm: 1 critical, 1 high, 0 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 nats's Vulert package health score?

Vulert scores nats 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of nats affected?

No. 2.29.3, 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.

Which version of nats should I use?

2.29.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does nats have?

2 vulnerabilities are recorded for nats in the npm ecosystem: 1 critical, 1 high, 0 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 nats vulnerabilities disclosed?

0 vulnerabilities were recorded for nats in the last 12 months, and the oldest entry in this database dates to 08 Oct 2020. 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 nats 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 nats for upcoming vulnerabilities?

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