VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

libp2p: vulnerability history, versions and safety

libp2p is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 23 releases, from Jul 2025 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M1 U2
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 19 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libp2p vulnerabilities

Vulert verdict on libp2p 0.8.1 i

Updated on 23 Oct 2026

Careful: 0.8.1 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.8.1 — affected i
  • Vulnerabilities on record 4 over 1 year · 3 in the last year i
  • Latest disclosure 19 Aug 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i
  • Stars 626 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence Apache-2.0 AND MIT i

Version list, release dates, licence and dependants published by PyPI, 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.8.1 22 Oct 2026 H1 U1 Apache-2.0 AND MIT No Details →
0.8.0 26 Sep 2026 H1 U1 Apache-2.0 AND MIT No Details →
0.7.0 09 Jul 2026 U1 Apache-2.0 AND MIT No Details →
0.6.0 16 Feb 2026 H1 U1 Apache-2.0 AND MIT No Details →
0.5.0 21 Dec 2025 H1 U1 Apache-2.0 AND MIT No Details →
0.4.0 05 Nov 2025 H1 U1 Apache-2.0 AND MIT No Details →
0.3.0 25 Sep 2025 H1 U1 Apache-2.0 AND MIT No Details →
0.2.9 09 Jul 2025 H1 U1 Apache-2.0 AND MIT No Details →
0.2.8 10 Jun 2025 H1 U1 Apache-2.0 AND MIT No Details →
0.2.7 22 May 2025 H1 U1 Apache-2.0 AND MIT No Details →
0.2.6 12 May 2025 H1 U1 Apache-2.0 AND MIT No Details →
0.2.5 14 Apr 2025 H1 U1 Apache-2.0 AND MIT No Details →
0.2.4 27 Mar 2025 H1 U1 non-standard No Details →
0.2.3 27 Mar 2025 H1 U1 non-standard No Details →
0.2.2 20 Feb 2025 H1 M1 U2 non-standard No Details →
0.2.1 20 Dec 2024 H1 M1 U2 non-standard No Details →
0.2.0 09 Jul 2024 H1 M1 U2 non-standard No Details →
0.1.5 25 Mar 2020 H1 M1 U2 non-standard No Details →
0.1.4 12 Dec 2019 H1 M1 U2 non-standard No Details →
0.1.3 28 Nov 2019 H1 M1 U2 non-standard No Details →
0.1.2 14 Nov 2019 H1 M1 U2 non-standard No Details →
0.1.1 11 Sep 2019 H1 M1 U2 non-standard No Details →
0.1.0a0 23 Oct 2018 H1 M1 U2 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for libp2p

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in libp2p: Oversized Data Frame Issue 7.5 high No fix published 24 Jul 2026
CVE-2026-73568: libp2p Oversized Data Frame Vulnerability Leading to DoS 7.5 high No fix published 19 Aug 2026
CVE-2025-29606: py-libp2p Vulnerable to DoS Attacks via Large RSA Keys 4.3 medium 0.2.3 14 Jul 2025
CVE-2025-29606: libp2p Vulnerable to DoS Attacks via Large RSA Keys 4.3 medium 0.2.3 07 Jul 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 libp2p

Is libp2p safe to use?

Vulert records 4 vulnerabilities for libp2p in PyPI: 0 critical, 1 high, 1 medium and 0 low, plus 2 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is libp2p's Vulert package health score?

Vulert scores libp2p 60/100, which reads as usable, but worth attention. 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 current release has a vulnerability with no published fix, which caps this score.

Is the latest version of libp2p affected?

Yes. 0.8.1, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does libp2p have?

4 vulnerabilities are recorded for libp2p in the PyPI ecosystem: 0 critical, 1 high, 1 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?

3 vulnerabilities were recorded for libp2p in the last 12 months, and the oldest entry in this database dates to 14 Jul 2025. 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.