# libp2p (PyPI) vulnerabilities

2 known vulnerabilities (1 high, 1 medium), with the versions each affects and the releases that fix them.

## At a glance

- Latest release: 0.8.1 (Oct 22, 2026): no advisory affects it
- Newest unaffected release: 0.8.1 (Oct 22, 2026), the latest release
- Weekly downloads: 600
- Dependents: 7
- Releases: 23 since 0.1.1 (Sep 11, 2019)
- Registry: https://pypi.org/project/libp2p/
- Releases read: Nov 8, 2026

## Version timeline

Affected versions per advisory, in version order:

- CVE-2026-73568: 0.1.0a0 to 0.7.0 (0.8.0 is outside it)
- CVE-2025-29606: 0.1.0a0 to 0.2.2 (0.2.3 is outside it)

## Advisories (2)

### [CVE-2026-73568](https://cve.now/CVE-2026-73568): py-libp2p: yamux connection DoS via oversized data frame

- Severity: High 7.5
- Published: Aug 13, 2026
- Affected: through 0.7.0.
- Fixed in 0.8.0 (released Sep 26, 2026, 44 days after disclosure), the first release outside every affected range (no listed fixed version clears them all).
- The latest release, 0.8.1, is not affected.

### [CVE-2025-29606](https://cve.now/CVE-2025-29606): py-libp2p before 0.2.3 allows a peer to cause a denial of service (resource consumption) via a large RSA key.

- Severity: Medium 4.3
- Published: Jul 14, 2025
- Affected: fixed in 0.2.3.
- Fixed in 0.2.3 (released Mar 27, 2025, 109 days before disclosure).
- The latest release, 0.8.1, is not affected.

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/packages/pypi/libp2p
Site guide for agents: https://cve.now/llms.txt
Uses NVD data; not endorsed by NVD.