CVE-2026-49866

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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

libp2p is a JavaScript Implementation of libp2p networking stack. Prior to 16.0.0, @libp2p/gossipsub defaultDecodeRpcLimits set maxIhaveMessageIDs and maxIwantMessageIDs to Infinity, allowing oversized IHAVE and IWANT control message arrays in message/decodeRpc.ts and gossipsub.ts to synchronously iterate roughly 180,000 message IDs per 4 MB frame and block the Node.js event loop. This issue is fixed in version 16.0.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

gossipsub: v16.0.0

Patch available: libp2p/js-libp2p gossipsub-v16.0.0

https://github.com/libp2p/js-libp2p/releases/tag/gossipsub-v16.0.0
github_commit Patch Available

commit 773dd80ded24 (libp2p/js-libp2p)

Patch available: libp2p/js-libp2p transport-interop-libp2p-main-v1.0.32 (contains commit 773dd80ded24)

https://github.com/libp2p/js-libp2p/commit/773dd80ded24dbd6b19e675c89fd2f3b45f2d899
github_pr Patch Available

fix(gossipsub)!: apply decodeRpcLimits to control messages

Patch available: libp2p/js-libp2p transport-interop-libp2p-main-v1.0.32 (PR #3520 merged 2026-05-26)

https://github.com/libp2p/js-libp2p/pull/3520
github Patch Available🟡 PoC Available

CPU DoS via oversized IHAVE and IWANT control message arrays · Advisory · libp2p/js-libp2p · GitHub

https://github.com/libp2p/js-libp2p/security/advisories/GHSA-cwc9-cp4j-mcvv

Vendor Advisories for CVE-2026-49866(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)
npm(1)
PackageVulnerable rangeFixed inDependents
@libp2p/gossipsub—16.0.0—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49866?
CVE-2026-49866 is a high vulnerability published on July 8, 2026. libp2p is a JavaScript Implementation of libp2p networking stack. Prior to 16.0.0, @libp2p/gossipsub defaultDecodeRpcLimits set maxIhaveMessageIDs and maxIwantMessageIDs to Infinity, allowing oversized IHAVE and IWANT control message arrays in message/decodeRpc.ts and gossipsub.ts to synchronously…
When was CVE-2026-49866 disclosed?
CVE-2026-49866 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49866 actively exploited?
CVE-2026-49866 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.4% of all scored CVEs.
What is the CVSS score of CVE-2026-49866?
CVE-2026-49866 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-49866?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49866, 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-49866

Explore →

Is Your Infrastructure Affected by CVE-2026-49866?

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

Start Free Scan →Browse All CVEs