VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

libp2p: vulnerability history, versions and safety

libp2p is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 79 releases, from Jul 2022 to Dec 2022. 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 H1 U2
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 libp2p vulnerabilities

Vulert verdict on libp2p 0.57.1 i

Updated on 23 Oct 2026

Good news: 0.57.1, 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 Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 0.57.1 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 07 Dec 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 5,623 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, 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 libp2p, 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
0.57.1 15 Oct 2026 none MIT — Details →
0.57.0 11 Sep 2026 none MIT — Details →
0.56.0 27 Jun 2025 none MIT — Details →
0.55.0 15 Jan 2025 none MIT — Details →
0.54.1 19 Aug 2024 none MIT — Details →
0.54.0 09 Aug 2024 none MIT — Details →
0.53.2 09 Dec 2023 none MIT — Details →
0.51.4 06 Dec 2023 none MIT — Details →
0.53.1 12 Nov 2023 none MIT — Details →
0.53.0 05 Nov 2023 none MIT — Details →
0.52.4 18 Oct 2023 none MIT — Details →
0.52.3 24 Aug 2023 none MIT — Details →
0.52.2 11 Aug 2023 none MIT — Details →
0.52.1 26 Jun 2023 none MIT — Details →
0.52.0 20 Jun 2023 none MIT — Details →
0.51.3 12 Apr 2023 none MIT — Details →
0.51.2 29 Mar 2023 none MIT — Details →
0.51.1 12 Mar 2023 none MIT — Details →
0.50.1 03 Mar 2023 none MIT — Details →
0.51.0 24 Feb 2023 none MIT — Details →
0.50.0 25 Nov 2022 none MIT — Details →
0.49.0 14 Oct 2022 none MIT — Details →
0.48.0 07 Sep 2022 none MIT — Details →
0.47.0 22 Aug 2022 none MIT — Details →
0.46.1 05 Jul 2022 none MIT — Details →
0.46.0 05 Jul 2022 none MIT — Details →
0.45.1 09 Jun 2022 none MIT — Details →
0.45.0 31 May 2022 H1 U2 MIT Yes Details →
0.44.0 04 Apr 2022 H1 U2 MIT Yes Details →
0.43.0 22 Feb 2022 H1 U2 MIT Yes Details →
0.41.2 07 Feb 2022 H1 U2 MIT Yes Details →
0.42.2 06 Feb 2022 H1 U2 MIT Yes Details →
0.42.1 02 Feb 2022 H1 U2 MIT Yes Details →
0.42.0 27 Jan 2022 H1 U2 MIT Yes Details →
0.41.1 10 Jan 2022 H1 U2 MIT Yes Details →
0.41.0 16 Nov 2021 H1 U2 MIT Yes Details →
0.40.0 01 Nov 2021 H1 U2 MIT Yes Details →
0.40.0-rc.3 27 Oct 2021 H1 U2 MIT Yes Details →
0.40.0-rc.2 15 Oct 2021 H1 U2 MIT Yes Details →
0.40.0-rc.1 15 Oct 2021 H1 U2 MIT Yes Details →
0.39.1 12 Jul 2021 H1 U2 MIT Yes Details →
0.39.0 12 Jul 2021 H1 U2 MIT Yes Details →
0.38.0 17 May 2021 H1 U2 MIT Yes Details →
0.37.1 14 Apr 2021 H1 U2 MIT Yes Details →
0.37.0 13 Apr 2021 H1 U2 MIT Yes Details →
0.36.0 17 Mar 2021 H1 U2 MIT Yes Details →
0.35.1 17 Feb 2021 H1 U2 MIT Yes Details →
0.35.0 15 Feb 2021 H1 U2 MIT Yes Details →
0.34.0 12 Jan 2021 H1 U2 MIT Yes Details →
0.33.0 18 Dec 2020 H1 U2 MIT Yes Details →
0.32.2 10 Dec 2020 H1 U2 MIT Yes Details →
0.32.1 09 Dec 2020 H1 U2 MIT Yes Details →
0.32.0 08 Dec 2020 H1 U2 MIT Yes Details →
0.31.2 02 Dec 2020 H1 U2 MIT Yes Details →
0.31.1 26 Nov 2020 H1 U2 MIT Yes Details →
0.31.0 25 Nov 2020 H1 U2 MIT Yes Details →
0.30.1 11 Nov 2020 H1 U2 MIT Yes Details →
0.30.0 09 Nov 2020 H1 U2 MIT Yes Details →
0.29.1 20 Oct 2020 H1 U2 MIT Yes Details →
0.29.0 16 Oct 2020 H1 U2 MIT Yes Details →
0.28.1 10 Sep 2020 H1 U2 MIT Yes Details →
0.28.0 09 Sep 2020 H1 U2 MIT Yes Details →
0.27.0 09 Sep 2020 H1 U2 MIT Yes Details →
0.26.0 09 Sep 2020 H1 U2 MIT Yes Details →
0.25.0 09 Sep 2020 H1 U2 MIT Yes Details →
0.24.0 18 Aug 2020 H1 U2 MIT Yes Details →
0.23.0 03 Aug 2020 H1 U2 MIT Yes Details →
0.22.0 17 Jul 2020 H1 U2 MIT Yes Details →
0.21.1 02 Jul 2020 H1 U2 MIT Yes Details →
0.21.0 01 Jul 2020 H1 U2 MIT Yes Details →
0.20.1 23 Jun 2020 H1 U2 MIT Yes Details →
0.20.0 22 Jun 2020 H1 U2 MIT Yes Details →
0.19.1 25 May 2020 H1 U2 MIT Yes Details →
0.19.0 18 May 2020 H1 U2 MIT Yes Details →
0.18.1 17 Apr 2020 H1 U2 MIT Yes Details →
0.18.0 09 Apr 2020 H1 U2 MIT Yes Details →
0.17.0 02 Apr 2020 H1 U2 MIT Yes Details →
0.16.2 28 Feb 2020 H1 U2 MIT Yes Details →
0.16.1 18 Feb 2020 H1 U2 MIT Yes Details →
0.16.0 14 Feb 2020 H1 U2 MIT Yes Details →
0.15.0 24 Jan 2020 H1 U2 MIT Yes Details →
0.14.0-alpha.1 07 Jan 2020 H1 U2 MIT Yes Details →
0.13.2 02 Jan 2020 H1 U2 MIT Yes Details →
0.13.1 13 Nov 2019 H1 U2 MIT Yes Details →
0.13.0 06 Nov 2019 H1 U2 MIT Yes Details →
0.12.0 15 Aug 2019 H1 U2 MIT Yes Details →
0.11.0 19 Jul 2019 H1 U2 MIT Yes Details →
0.10.0 25 Jun 2019 H1 U2 MIT Yes Details →
0.9.2 25 Jun 2019 H1 U2 MIT Yes Details →
0.9.1 05 Jun 2019 H1 U2 MIT Yes Details →
0.9.0 04 Jun 2019 H1 U2 MIT Yes Details →
0.8.1 15 May 2019 H1 U2 MIT Yes Details →
0.8.0 15 May 2019 H1 U2 MIT Yes Details →
0.7.0 23 Apr 2019 H1 U2 MIT Yes Details →
0.6.0 29 Mar 2019 H1 U2 MIT Yes Details →
0.5.0 13 Mar 2019 H1 U2 MIT Yes Details →
0.4.2 27 Feb 2019 H1 U2 MIT Yes Details →
0.4.1 20 Feb 2019 H1 U2 MIT Yes Details →
0.4.0 20 Feb 2019 H1 U2 MIT Yes Details →
0.3.1 04 Feb 2019 H1 U2 MIT Yes Details →
0.3.0 30 Jan 2019 H1 U2 — Yes Details →
0.2.2 14 Jan 2019 H1 U2 — Yes Details →
0.2.1 14 Jan 2019 H1 U2 — Yes Details →
0.2.0 10 Jan 2019 H1 U2 — Yes Details →
0.1.0 02 Jan 2019 H1 U2 — Yes Details →
0.0.1 08 Aug 2018 H1 U2 — Yes Details →

All 106 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 3

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

03 Vulnerabilities

Recorded vulnerabilities for libp2p

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-23486: libp2p DoS vulnerability from lack of resource management 7.5 high 0.45.1 12 Jul 2022
CVE-2022-23486: libp2p Lack of resource management DoS 7.5 high 0.45.1 12 Jul 2022
CVE-2022-23486: libp2p DoS vulnerability from lack of resource management 7.5 high 0.45.1 07 Dec 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 libp2p

Is libp2p safe to use?

Vulert records 3 vulnerabilities for libp2p in crates.io: 0 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is libp2p's Vulert package health score?

Vulert scores libp2p 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 libp2p affected?

No. 0.57.1, 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 libp2p have?

3 vulnerabilities are recorded for libp2p in the crates.io ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libp2p vulnerabilities disclosed?

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

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