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.
CVE-2026-61544
HIGHPre-NVD 8.28.2—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 68(Attend)EG Risk 68/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 17, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
github_commit Patch Available
commit e8f35e12c241 (libp2p/rust-libp2p)
Patch available: libp2p/rust-libp2p v0.57.0 (contains commit e8f35e12c241)
https://github.com/libp2p/rust-libp2p/commit/e8f35e12c2418b04df6e9cdf036005e8aee3c7a2github_commit
commit 212f3774af04 (libp2p/rust-libp2p)
Fix landed in libp2p/rust-libp2p commit 212f3774af04 — awaiting tagged release
https://github.com/libp2p/rust-libp2p/commit/212f3774af048e2cecfb2e6b1e08477685e52b22github_pr Patch Available
fix(quic): avoid panic on post-handshake cert validation
Patch available: libp2p/rust-libp2p v0.57.0 (PR #6525 merged 2026-07-17)
https://github.com/libp2p/rust-libp2p/pull/6525github Patch Available🟡 PoC Available
Remote panic in libp2p-quic via certificate expiry race during QUIC handshake · Advisory · libp2p/rust-libp2p · GitHub
https://github.com/libp2p/rust-libp2p/security/advisories/GHSA-5hq8-qhww-jm7qVendor Advisories for CVE-2026-61544(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libp2p-quic | — | 0.13.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 04:26 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:34 UTCEG score recompute
- 2026-09-17 18:08 UTCEG score recompute
- 2026-09-16 20:12 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 20:39 UTCEG score recompute
- 2026-09-15 19:58 UTCEG score recompute
- 2026-09-15 19:57 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-61544?
CVE-2026-61544 is a high vulnerability published on September 15, 2026. 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…
When was CVE-2026-61544 disclosed?
CVE-2026-61544 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61544 actively exploited?
CVE-2026-61544 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.8% of all scored CVEs.
What is the CVSS score of CVE-2026-61544?
CVE-2026-61544 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-61544?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61544, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61544
Is Your Infrastructure Affected by CVE-2026-61544?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.