Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5hq8-qhww-jm7q | libp2p-quic: Remote panic via certificate expiry race during QUIC handshake |
Tue, 15 Sep 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | libp2p-quic: Remote panic via certificate expiry race during QUIC handshake | |
| Weaknesses | CWE-248 | |
| References |
| |
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-15T19:46:13.721Z
Reserved: 2026-07-10T16:27:03.093Z
Link: CVE-2026-61544
No data.
Status : Received
Published: 2026-09-15T20:17:35.147
Modified: 2026-09-15T20:17:35.147
Link: CVE-2026-61544
No data.
OpenCVE Enrichment
No data.
Github GHSA