VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@chainsafe/libp2p-noise: vulnerability history, versions and safety

@chainsafe/libp2p-noise is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 3 releases, first recorded in Mar 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded 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 @chainsafe/libp2p-noise vulnerabilities

Vulert verdict on @chainsafe/libp2p-noise 17.0.0 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 17.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 18 Mar 2022 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Depended on by 287 packages i
  • Stars 43 i
  • Last release 12 months ago i
  • Licence Apache-2.0 OR 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 @chainsafe/libp2p-noise, 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
17.0.0 25 Sep 2025 none Apache-2.0 OR MIT — Details →
16.1.5 22 Sep 2025 none Apache-2.0 OR MIT — Details →
16.1.4 26 Jun 2025 none Apache-2.0 OR MIT — Details →
16.1.3 23 Apr 2025 none Apache-2.0 OR MIT — Details →
16.1.2 16 Apr 2025 none Apache-2.0 OR MIT — Details →
16.1.1 16 Apr 2025 none Apache-2.0 OR MIT — Details →
16.1.0 20 Mar 2025 none Apache-2.0 OR MIT — Details →
16.0.3 21 Feb 2025 none Apache-2.0 OR MIT — Details →
16.0.2 20 Feb 2025 none Apache-2.0 OR MIT — Details →
16.0.1 21 Jan 2025 none Apache-2.0 OR MIT — Details →
16.0.0 11 Sep 2024 none Apache-2.0 OR MIT — Details →
15.1.2 30 Aug 2024 none Apache-2.0 OR MIT — Details →
15.1.1 13 Aug 2024 none Apache-2.0 OR MIT — Details →
15.1.0 25 Jun 2024 none Apache-2.0 OR MIT — Details →
15.0.0 17 Jan 2024 none Apache-2.0 OR MIT — Details →
14.1.0 11 Dec 2023 none Apache-2.0 OR MIT — Details →
14.0.0 29 Nov 2023 none Apache-2.0 OR MIT — Details →
13.0.5 27 Nov 2023 none Apache-2.0 OR MIT — Details →
13.0.4 24 Nov 2023 none Apache-2.0 OR MIT — Details →
13.0.3 13 Nov 2023 none Apache-2.0 OR MIT — Details →
13.0.2 23 Oct 2023 none Apache-2.0 OR MIT — Details →
13.0.1 05 Sep 2023 none Apache-2.0 OR MIT — Details →
13.0.0 03 Aug 2023 none Apache-2.0 OR MIT — Details →
12.0.2 19 Jul 2023 none Apache-2.0 OR MIT — Details →
12.0.1 22 May 2023 none Apache-2.0 OR MIT — Details →
12.0.0 08 May 2023 none Apache-2.0 OR MIT — Details →
11.0.4 31 Mar 2023 none Apache-2.0 OR MIT — Details →
11.0.2 27 Mar 2023 none Apache-2.0 OR MIT — Details →
11.0.1 20 Feb 2023 none Apache-2.0 OR MIT — Details →
11.0.0 09 Jan 2023 none Apache-2.0 OR MIT — Details →
10.2.0 22 Nov 2022 none Apache-2.0 OR MIT — Details →
10.1.0 15 Nov 2022 none Apache-2.0 OR MIT — Details →
10.0.1 02 Nov 2022 none Apache-2.0 OR MIT — Details →
10.0.0 19 Oct 2022 none Apache-2.0 OR MIT — Details →
9.0.0 07 Oct 2022 none Apache-2.0 OR MIT — Details →
8.0.2 04 Oct 2022 none Apache-2.0 OR MIT — Details →
8.0.1 19 Aug 2022 none Apache-2.0 OR MIT — Details →
8.0.0 11 Aug 2022 none Apache-2.0 OR MIT — Details →
7.0.3 03 Aug 2022 none Apache-2.0 OR MIT — Details →
7.0.2 02 Aug 2022 none Apache-2.0 OR MIT — Details →
7.0.1 23 Jun 2022 none Apache-2.0 OR MIT — Details →
7.0.0 17 Jun 2022 none Apache-2.0 OR MIT — Details →
6.2.0 24 May 2022 none Apache-2.0 OR MIT — Details →
6.1.1 14 Apr 2022 none Apache-2.0 OR MIT — Details →
6.1.0 11 Apr 2022 none MIT — Details →
6.0.1 22 Mar 2022 none MIT — Details →
6.0.0 17 Mar 2022 none MIT — Details →
4.1.2 11 Mar 2022 none MIT — Details →
5.0.3 09 Mar 2022 none MIT — Details →
5.0.2 14 Jan 2022 none MIT — Details →
5.0.1 06 Jan 2022 none MIT — Details →
5.0.0 06 Dec 2021 none MIT — Details →
4.1.1 02 Sep 2021 H1 MIT Yes Details →
4.1.0 18 Aug 2021 H1 MIT Yes Details →
4.0.0 29 Jul 2021 H1 MIT Yes Details →

All 55 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for @chainsafe/libp2p-noise

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-24759: Failure to validate signature during handshake in @chainsafe/libp2p-noise 8.1 high 4.1.2 18 Mar 2022

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 @chainsafe/libp2p-noise

Is @chainsafe/libp2p-noise safe to use?

Vulert records 1 vulnerabilities for @chainsafe/libp2p-noise in npm: 0 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 @chainsafe/libp2p-noise's Vulert package health score?

Vulert scores @chainsafe/libp2p-noise 77/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 @chainsafe/libp2p-noise affected?

No. 17.0.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.

Which version of @chainsafe/libp2p-noise should I use?

17.0.0 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 @chainsafe/libp2p-noise have?

1 vulnerability is recorded for @chainsafe/libp2p-noise in the npm ecosystem: 0 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 @chainsafe/libp2p-noise vulnerabilities disclosed?

0 vulnerabilities were recorded for @chainsafe/libp2p-noise in the last 12 months, and the oldest entry in this database dates to 18 Mar 2022. 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 @chainsafe/libp2p-noise 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 @chainsafe/libp2p-noise for upcoming vulnerabilities?

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