CVE-2026-61544

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-79501 (ENISA EUVD) · GHSA-5hq8-qhww-jm7q (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
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/e8f35e12c2418b04df6e9cdf036005e8aee3c7a2
GitHub commit

commit 212f3774af04 (libp2p/rust-libp2p)

Fix landed in libp2p/rust-libp2p commit 212f3774af04 — awaiting tagged release

https://github.com/libp2p/rust-libp2p/commit/212f3774af048e2cecfb2e6b1e08477685e52b22
GitHub pull request 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/6525
GitHub advisoryMentions a patch (unverified)

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-jm7q

Vendor 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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustlibp2p-quic @ 0.13.1 (fixes < 0.13.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
libp2p-quic—
  • every version up to 0.13.1: fixed in 0.13.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-5hq8-qhww-jm7q · GitHub severity HIGH
  3. 2026-11-01 07:41 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-28 06:56 UTCEG score recompute
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-25 14:14 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-20 18:53 UTCEG score recompute
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-10-18 03:25 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 55 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-13 13:25 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-12 15:50 UTCEG score recompute
  5. 2026-10-11 19:34 UTCEG score recompute
  6. 2026-10-11 16:49 UTCEG score recompute
  7. 2026-10-11 14:11 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-11 05:30 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-10 03:08 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-08 22:09 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-08 10:01 UTCEG score recompute
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-06 23:39 UTCEG score recompute
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-10-06 00:46 UTCEG score recompute
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-05 01:50 UTCEG score recompute
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-03 15:10 UTCEG score recompute
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-03 03:44 UTCEG score recompute
  26. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  27. 2026-10-02 04:47 UTCEG score recompute
  28. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  29. 2026-09-30 18:09 UTCEG score recompute
  30. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  31. 2026-09-29 20:18 UTCEG score recompute
  32. 2026-09-29 05:56 UTCEG score recompute
  33. 2026-09-28 18:30 UTCEG score recompute
  34. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  35. 2026-09-27 18:53 UTCEG score recompute
  36. 2026-09-26 19:58 UTCEG score recompute
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-09-26 08:24 UTCEG score recompute
  39. 2026-09-24 22:05 UTCEG score recompute
  40. 2026-09-23 23:11 UTCEG score recompute
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  42. 2026-09-23 00:04 UTCEG score recompute
  43. 2026-09-22 01:11 UTCEG score recompute
  44. 2026-09-21 02:15 UTCEG score recompute
  45. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-09-19 15:56 UTCEG score recompute
  47. 2026-09-19 04:26 UTCEG score recompute
  48. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-09-18 05:34 UTCEG score recompute
  50. 2026-09-17 18:08 UTCEG score recompute
  51. 2026-09-16 20:12 UTCEG score recompute
  52. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-09-15 20:39 UTCEG score recompute
  54. 2026-09-15 19:58 UTCEG score recomputeFirst assessed: 8.2 HIGH
  55. 2026-09-15 19:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61544?
CVE-2026-61544 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-61544 published?
The CVE record for CVE-2026-61544 was published on September 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-61544 actively exploited?
CVE-2026-61544 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61544?
CVE-2026-61544 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61544?
A fix for CVE-2026-61544 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61544 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61544

Explore →

Is Your Infrastructure Affected by CVE-2026-61544?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs