CVE-2026-119793

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-127198 (ENISA EUVD) · GHSA-x2vm-cf3p-m2w8 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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.6%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 17.0.0, the @libp2p/gossipsub default configuration allows a connected remote peer to submit unsigned subscription RPC metadata for arbitrarily many distinct topic strings. handleReceivedSubscription in packages/gossipsub/src/gossipsub.ts creates a persistent topics-map entry for each accepted topic, while allowedTopics is unset by default, decodeRpc maxSubscriptions limits only one RPC rather than aggregate topic bytes, and peer scoring has no subscription-volume penalty. A single peer can therefore grow the topics map and committed heap toward out-of-memory conditions, and disconnecting additionally causes removePeer to scan all accumulated topic entries. This issue is fixed in version 17.0.0.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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.6%
EPSS %ILE
50th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS. 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

November 17, 2026

Last Modified

November 18, 2026

Advisory Details (4)

Auto-updated Nov 17, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config · Advisory · libp2p/js-libp2p · GitHub

https://github.com/libp2p/js-libp2p/security/advisories/GHSA-x2vm-cf3p-m2w8
GitHub release Patch Available

gossipsub: v17.0.0

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

https://github.com/libp2p/js-libp2p/releases/tag/gossipsub-v17.0.0
GitHub pull request Patch Available

fix(gossipsub)!: bound subscribed topic bytes per peer

Patch available: libp2p/js-libp2p transport-interop-libp2p-main-v1.0.45 (PR #3593 merged 2026-08-13)

https://github.com/libp2p/js-libp2p/pull/3593
GitHub commit Patch Available

commit d5534174d8b7 (libp2p/js-libp2p)

Patch available: libp2p/js-libp2p transport-interop-libp2p-main-v1.0.45 (contains commit d5534174d8b7)

https://github.com/libp2p/js-libp2p/commit/d5534174d8b7d23ac1bd45a7e738664fbfb0cf4c

Vendor Advisories for CVE-2026-119793(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
npm@libp2p/gossipsub @ 17.0.0 (fixes < 17.0.0)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@libp2p/gossipsub—
  • every version up to 17.0.0: fixed in 17.0.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  3. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-19 15:26 UTCOSV refresh
  5. 2026-11-18 17:43 UTCEchelonGraph re-scored
  6. 2026-11-18 17:43 UTCGHSA enrichmentGHSA-x2vm-cf3p-m2w8 · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-11-18 17:28 UTCEchelonGraph re-scored
  8. 2026-11-18 17:28 UTCGHSA enrichmentGHSA-x2vm-cf3p-m2w8 · GitHub severity HIGH · GitHub CVSS 7.5
  9. 2026-11-18 16:43 UTCEchelonGraph re-scored
  10. 2026-11-18 16:43 UTCGHSA enrichmentGHSA-x2vm-cf3p-m2w8 · GitHub severity HIGH · GitHub CVSS 7.5
  11. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-11-17 21:53 UTCEchelonGraph re-scored
  13. 2026-11-17 21:53 UTCGHSA enrichmentGHSA-x2vm-cf3p-m2w8 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-17 20:03 UTCENISA EUVD ID recordedEUVD-2026-127198 · Source: ENISA EUVD
  15. 2026-11-17 19:19 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  16. 2026-11-17 19:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-119793?
CVE-2026-119793 is a high-severity vulnerability; its CVE record was published on November 17, 2026. libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 17.0.0, the @libp2p/gossipsub default configuration allows a connected remote peer to submit unsigned subscription RPC metadata for arbitrarily many distinct topic strings. handleReceivedSubscription in…
When was the CVE record for CVE-2026-119793 published?
The CVE record for CVE-2026-119793 was published on November 17, 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 November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-119793 actively exploited?
CVE-2026-119793 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119793?
CVE-2026-119793 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119793?
A fix for CVE-2026-119793 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119793 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-119793

Explore →

Is Your Infrastructure Affected by CVE-2026-119793?

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