CVE-2026-73568

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

py-libp2p is the Python implementation of the libp2p networking stack. In 0.7.0 and earlier, the yamux handle_incoming() method in libp2p/stream_muxer/yamux/yamux.py reads an attacker-controlled 32-bit DATA frame length with read_exactly() before validating it against MAX_WINDOW_SIZE or checking whether stream_id exists. A peer that completes the standard Noise handshake can send a 12-byte frame declaring a 0xFFFFFFFF body and then withhold the body, causing the sequential yamux read loop used by the default new_host() configuration to block and preventing every stream on that connection from making progress. No fixed version is available as of this review.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

August 13, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 146ea87d1a20 (libp2p/py-libp2p)

Fix landed in libp2p/py-libp2p commit 146ea87d1a20 — awaiting tagged release

https://github.com/libp2p/py-libp2p/commit/146ea87d1a20cc7dacf684ecf7c204543be04b37
github Patch Available🟡 PoC Available

yamux connection DoS via oversized data frame · Advisory · libp2p/py-libp2p · GitHub

https://github.com/libp2p/py-libp2p/security/advisories/GHSA-hmj8-5xmh-5573

Vendor Advisories for CVE-2026-73568(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 / EcosystemFixed in / PatchReleasedSource
piplibp2p—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)
PyPI(1)
PackageVulnerable rangeFixed inDependents
libp2p0.1.0a0 ... 0.7.0 (21 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 103× 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.

Showing the most recent 100 of 139 total refreshes for this CVE.

  1. 2026-09-20 15:54 UTCGHSA enrichment
  2. 2026-09-20 00:10 UTCEG score recompute
  3. 2026-09-20 00:10 UTCGHSA enrichment
  4. 2026-09-19 11:13 UTCGHSA enrichment
  5. 2026-09-18 20:25 UTCEG score recompute
  6. 2026-09-18 20:24 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 15:11 UTCGHSA enrichment
  9. 2026-09-18 02:15 UTCEG score recompute
  10. 2026-09-18 02:15 UTCGHSA enrichment
  11. 2026-09-17 13:18 UTCGHSA enrichment
  12. 2026-09-16 23:59 UTCEG score recompute
  13. 2026-09-16 23:59 UTCGHSA enrichment
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 05:37 UTCEG score recompute
  16. 2026-09-16 05:37 UTCGHSA enrichment
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 16:41 UTCGHSA enrichment
  19. 2026-09-15 03:36 UTCEG score recompute
  20. 2026-09-15 03:35 UTCGHSA enrichment
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 14:38 UTCGHSA enrichment
  23. 2026-09-14 01:35 UTCEG score recompute
  24. 2026-09-14 01:35 UTCGHSA enrichment
  25. 2026-09-13 12:38 UTCGHSA enrichment
Show 75 more
  1. 2026-09-12 23:39 UTCEG score recompute
  2. 2026-09-12 23:39 UTCGHSA enrichment
  3. 2026-09-12 15:02 UTCEPSS rescore
  4. 2026-09-12 10:42 UTCGHSA enrichment
  5. 2026-09-11 21:41 UTCEG score recompute
  6. 2026-09-11 21:41 UTCGHSA enrichment
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 08:44 UTCGHSA enrichment
  9. 2026-09-10 19:47 UTCEG score recompute
  10. 2026-09-10 19:47 UTCGHSA enrichment
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-10 06:50 UTCGHSA enrichment
  13. 2026-09-09 17:53 UTCGHSA enrichment
  14. 2026-09-09 04:56 UTCEG score recompute
  15. 2026-09-09 04:56 UTCGHSA enrichment
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-07 20:16 UTCEG score recompute
  18. 2026-09-07 20:16 UTCGHSA enrichment
  19. 2026-09-07 07:19 UTCGHSA enrichment
  20. 2026-09-06 18:19 UTCEG score recompute
  21. 2026-09-06 18:19 UTCGHSA enrichment
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-06 05:22 UTCGHSA enrichment
  24. 2026-09-05 16:26 UTCEG score recompute
  25. 2026-09-05 16:25 UTCGHSA enrichment
  26. 2026-09-05 03:27 UTCGHSA enrichment
  27. 2026-09-04 14:30 UTCEG score recompute
  28. 2026-09-04 14:30 UTCGHSA enrichment
  29. 2026-09-04 05:07 UTCEPSS rescore
  30. 2026-09-04 01:33 UTCGHSA enrichment
  31. 2026-09-03 12:34 UTCGHSA enrichment
  32. 2026-09-02 23:10 UTCEG score recompute
  33. 2026-09-02 23:10 UTCGHSA enrichment
  34. 2026-09-02 14:12 UTCEPSS rescore
  35. 2026-09-02 04:23 UTCGHSA enrichment
  36. 2026-09-01 15:12 UTCEG score recompute
  37. 2026-09-01 15:11 UTCGHSA enrichment
  38. 2026-09-01 13:54 UTCEPSS rescore
  39. 2026-09-01 04:40 UTCEPSS rescore
  40. 2026-09-01 04:40 UTCEPSS rescore
  41. 2026-09-01 00:38 UTCGHSA enrichment
  42. 2026-08-31 11:38 UTCGHSA enrichment
  43. 2026-08-30 22:25 UTCEG score recompute
  44. 2026-08-30 22:25 UTCGHSA enrichment
  45. 2026-08-30 19:18 UTCEPSS rescore
  46. 2026-08-30 19:17 UTCEPSS rescore
  47. 2026-08-30 09:28 UTCEG score recompute
  48. 2026-08-30 09:28 UTCGHSA enrichment
  49. 2026-08-30 01:22 UTCEPSS rescore
  50. 2026-08-29 20:30 UTCGHSA enrichment
  51. 2026-08-29 07:33 UTCEG score recompute
  52. 2026-08-29 07:33 UTCGHSA enrichment
  53. 2026-08-28 21:42 UTCEPSS rescore
  54. 2026-08-28 10:08 UTCGHSA enrichment
  55. 2026-08-27 21:01 UTCEG score recompute
  56. 2026-08-27 21:01 UTCGHSA enrichment
  57. 2026-08-27 14:25 UTCEPSS rescore
  58. 2026-08-27 08:04 UTCGHSA enrichment
  59. 2026-08-26 19:06 UTCEG score recompute
  60. 2026-08-26 19:06 UTCGHSA enrichment
  61. 2026-08-26 14:47 UTCEPSS rescore
  62. 2026-08-26 06:10 UTCGHSA enrichment
  63. 2026-08-25 17:12 UTCEG score recompute
  64. 2026-08-25 17:12 UTCGHSA enrichment
  65. 2026-08-25 13:49 UTCEPSS rescore
  66. 2026-08-25 04:06 UTCGHSA enrichment
  67. 2026-08-24 15:09 UTCEG score recompute
  68. 2026-08-24 15:09 UTCGHSA enrichment
  69. 2026-08-24 02:12 UTCEG score recompute
  70. 2026-08-24 02:12 UTCGHSA enrichment
  71. 2026-08-23 13:11 UTCEG score recompute
  72. 2026-08-23 13:11 UTCGHSA enrichment
  73. 2026-08-23 00:19 UTCEPSS rescore
  74. 2026-08-23 00:07 UTCGHSA enrichment
  75. 2026-08-22 11:11 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73568?
CVE-2026-73568 is a high vulnerability published on August 13, 2026. py-libp2p is the Python implementation of the libp2p networking stack. In 0.7.0 and earlier, the yamux handleincoming() method in libp2p/streammuxer/yamux/yamux.py reads an attacker-controlled 32-bit DATA frame length with readexactly() before validating it against MAXWINDOWSIZE or checking whether…
When was CVE-2026-73568 disclosed?
CVE-2026-73568 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73568 actively exploited?
CVE-2026-73568 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 64.5% of all scored CVEs.
What is the CVSS score of CVE-2026-73568?
CVE-2026-73568 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-73568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73568, 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-73568

Explore →

Is Your Infrastructure Affected by CVE-2026-73568?

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

Start Free Scan →Browse All CVEs