Vulnerability in libp2p-quic (CVE-2026-61544)
Summary
Vulnerability in libp2p-quic (CVE-2026-61544). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.13.1 or later.
Original description
The description as published by the source.
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:
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:
- Opening a QUIC connection to a libp2p QUIC listener.
- Presenting a valid libp2p TLS certificate with a very short lifetime.
- Allowing the initial handshake-time certificate validation to succeed.
- Withholding the final client handshake fragment packet until after the certificate expires, but before the QUIC handshake timeout elapses.
- The listener completes the handshake and hits the post-handshake certificate re-parse, which panics.
Impa…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61544 has been found in libp2p-quic.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libp2p-quic to 0.13.1 or later.
If unsure, ask your IT team or search "libp2p-quic CVE-2026-61544" on the vendor's site.
CVE-2026-61544 (libp2p-quic) — CWE-248
Patched: 0.13.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-248) exists in libp2p-quic.
Check the vendor advisory for the affected versions of libp2p-quic.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.13.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libp2p-quic' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'libp2p-quic' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libp2p-quicを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade libp2p-quic to 0.13.1ステージング環境で 0.13.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com