cve.bz

CVE-2026-61544 libp2p rust-libp2p: Uncaught Exception

8.2 highEPSS 0.3%Fix available

High (8.2) in libp2p rust-libp2p. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in libp2p-quic 0.13.1.

On this page
libp2p-rust is the official Rust language implementation of the libp2p networking stack. Prior to 0.13.1, libp2p-quic could panic during an inbound QUIC handshake when a remote peer presented a valid short-lived libp2p TLS certificate and delayed the final TLS 1.3 handshake fragment until after the certificate expired. In the Quinn post-handshake upgrade path, transports/quic/src/connection/connecting.rs called libp2p_tls::certificate::parse a second time in remote_peer_id and used expect on the result. The repeated wall-clock validity check could reject the now-expired certificate, causing the expect call to terminate any application exposing an affected libp2p-quic listener. This vulnerability is fixed in 0.13.1.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-09-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-248 Uncaught Exception
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • libp2p-quic (crates.io): fixed in 0.13.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-61544 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61544?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61544?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61544 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
libp2p rust-libp2p< 0.13.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5hq8-qhww-jm7qcrates.iolibp2p-quic<0.13.10.13.1
RUSTSEC-2026-0525crates.iolibp2p-quic>=0.0.0-0 <0.13.10.13.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.04:LTS, 26.10rust-libp2p-identityno fix listedUBUNTU-CVE-2026-61544

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

References

Check your stackJSON