Advisory

RUSTSEC-2026-0525

Also known as: CVE-2026-61544, GHSA-5hq8-qhww-jm7q

Summary

Remote panic when a peer certificate expires during the QUIC handshake

Details

After the QUIC handshake finished, the peer's libp2p TLS certificate was parsed a second time to get its peer ID, and the result was unwrapped with expect, on the assumption that it could not fail because the certificate had already been validated. Parsing checks the certificate's validity period again against the current time. A remote peer can present a certificate that is about to expire and delay the end of the handshake until it has expired, so the second parse fails and the process panics. No authentication is needed; any application with a reachable QUIC listener is affected.

The fix returns a connection error instead of panicking when the peer identity or certificate cannot be read after the handshake. It is in 0.13.1, and was backported to the main branch in libp2p/rust-libp2p#6525 for 0.14.0.

Severity

Not rated by the source.

Dates

Published
2026-07-10 12:00 UTC
Modified
2026-11-13 12:45 UTC

Affected packages and fixes

libp2p-quic

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.13.1 (semver)

Fixed versions

0.13.1

Fix

  • Fixed version 0.13.1
    cargo update -p libp2p-quic --precise 0.13.1

Fix 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

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences