CVE-2026-103936

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th 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

Also known asEUVD-2026-102224 (ENISA EUVD)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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 6.0.28, the @libp2p/webrtc webRTCDirect() Node.js listener processes unauthenticated STUN Binding Requests before PeerId authentication, Noise, muxing, protocol negotiation, connection creation, or connection-manager admission. The listener in packages/transport-webrtc/src/private-to-public/utils/stun-listener.ts forwards the packet-controlled request.ufrag into DirectRTCPeerConnection.setLocalDescription, where the value is reused as an ICE password without validating its required length and character set. A short credential causes node-datachannel or libdatachannel to raise an uncaught native invalid_argument and abort the process with SIGABRT, allowing a single remote UDP packet to deny service. The confirmed impact is process termination only, with no demonstrated memory corruption, code execution, browser impact, confidentiality impact, integrity impact, or connection-limit bypass. This issue is fixed in version 6.0.28.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.5%
EPSS %ILE
44th
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 none (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

October 15, 2026

Last Modified

October 16, 2026

Advisory Details (4)

Auto-updated Oct 15, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

webrtc: v6.0.28

Patch available: libp2p/js-libp2p webrtc-v6.0.28

https://github.com/libp2p/js-libp2p/releases/tag/webrtc-v6.0.28
GitHub commit Patch Available

commit 68794c8e2e67 (libp2p/js-libp2p)

Patch available: libp2p/js-libp2p transport-interop-libp2p-main-v1.0.42 (contains commit 68794c8e2e67)

https://github.com/libp2p/js-libp2p/commit/68794c8e2e67d5f38da59e379dc051b2789e46f6
GitHub pull request Patch Available

fix(transport-webrtc): validate ufrag from incoming STUN requests

Patch available: libp2p/js-libp2p transport-interop-libp2p-main-v1.0.42 (PR #3584 merged 2026-07-26)

https://github.com/libp2p/js-libp2p/pull/3584
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Single pre-auth STUN packet terminates `@libp2p/webrtc` WebRTC-direct Node.js listeners · Advisory · libp2p/js-libp2p · GitHub

https://github.com/libp2p/js-libp2p/security/advisories/GHSA-x3m2-6mg8-vj7f

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 27× 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-02 16:43 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-29 14:28 UTCEG score recompute
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-25 14:56 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-23 05:19 UTCEG score recompute
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-18 05:09 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-16 18:30 UTCEG score recompute
  23. 2026-10-16 17:22 UTCEG score recompute
  24. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-10-15 18:28 UTCEG score recompute
Show 2 more
  1. 2026-10-15 17:34 UTCEG score recomputeFirst assessed: 7.5 HIGH
  2. 2026-10-15 17:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-103936?
CVE-2026-103936 is a high-severity vulnerability; its CVE record was published on October 15, 2026. libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 6.0.28, the @libp2p/webrtc webRTCDirect() Node.js listener processes unauthenticated STUN Binding Requests before PeerId authentication, Noise, muxing, protocol negotiation, connection creation, or connection-manager…
When was the CVE record for CVE-2026-103936 published?
The CVE record for CVE-2026-103936 was published on October 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-103936 actively exploited?
CVE-2026-103936 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103936?
CVE-2026-103936 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-103936?
A fix for CVE-2026-103936 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-103936

Explore →

Is Your Infrastructure Affected by CVE-2026-103936?

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