Skip to content
skopnix

NVD published 15 Sep 2026

CVE-2026-61544

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.

Signals

KEV, exploited in the wild
no
EPSS, 30-day forecast
0.3%, 21th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

Not in CISA's catalogue as of the last daily pull. Absence is not proof of safety. No score published by NVD.

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 1 dispatch

  1. GHSA-5hq8-qhww-jm7q: libp2p-quic: Remote panic via certificate expiry race during QUIC handshake

Public exploit code none in our sources

No public exploit in the sources we track: GitHub proof-of-concept lists, Metasploit and Exploit-DB. Absence is not proof that none exists.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check