libp2p-quic
Affected
- introduced
0, fixed0.13.1(semver)
Fixed versions
0.13.1
Fix
- Fixed version
0.13.1cargo update -p libp2p-quic --precise 0.13.1
Advisory
Also known as: CVE-2026-61544, RUSTSEC-2026-0525
libp2p-quic: Remote panic via certificate expiry race during QUIC handshake
Summary
libp2p-quic can panic on an inbound QUIC handshake if a malicious peer presents a valid, short lived libp2p TLS certificate and delays the final TLS 1.3 handshake fragment until the certificate expires.
This is remotely reachable by a network peer and can crash applications exposing a libp2p QUIC listener.
Details
During the TLS handshake, libp2p-tls parses and validates the peer certificate. After Quinn reports handshake completion, libp2p-quic re-parses the same certificate in the post-handshake upgrade path and assumes this cannot fail:
https://github.com/libp2p/rust-libp2p/blob/969b707bf1177ebebd1febc285c3fd22793b95c5/transports/quic/src/connection/connecting.rs#L65-L66
However, libp2p_tls::certificate::parse() re-runs certificate verification on every call, including a wall-clock validity check. A certificate that was valid during the first handshake time parse can expire before the second post-handshake parse, causing the expect(...) to panic.
PoC
A malicious peer can trigger this by:
Impact
Remote unauthenticated denial of service. Any application exposing an affected libp2p-quic listener can be crashed by a network peer that performs a valid-looking QUIC/TLS handshake with attacker-controlled timing. No malformed packets are required.
High Basis: The source's own band: HIGH
0, fixed 0.13.1 (semver)0.13.1
0.13.1cargo update -p libp2p-quic --precise 0.13.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0