CVE-2026-106357

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

Use after free in WebRTC in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS v3
8.8
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 6, 2026

Last Modified

October 7, 2026

Advisory Details (1)

Auto-updated Oct 6, 2026
No fix on record yet.
Web page

Chromium

https://issues.chromium.org/issues/567160162

Vendor Advisories for CVE-2026-106357(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 154.0.8037.92-1~deb13u1 (431 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 154.0.8037.92-1~deb13u1 (196 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 154.0.8037.92-1~deb13u1 (196 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 33× 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-10-11 20:14 UTCEG score recompute
  2. 2026-10-11 18:27 UTCEG score recompute
  3. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  4. 2026-10-11 13:42 UTCEG score recompute
  5. 2026-10-11 13:42 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-10-11 01:57 UTCEG score recompute
  7. 2026-10-11 01:57 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-10-10 14:19 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-10 02:41 UTCEG score recompute
  11. 2026-10-10 02:40 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-10-09 15:02 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-09 02:55 UTCEG score recompute
  15. 2026-10-09 02:55 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-08 15:17 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-08 03:39 UTCEG score recompute
  19. 2026-10-08 03:39 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-10-07 16:01 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-07 04:20 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-07 04:02 UTCEG score recompute
  24. 2026-10-07 04:02 UTCGHSA enrichmentGHSA-qgq7-9f49-wxv2 · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-06 20:34 UTCEG score recompute
Show 8 more
  1. 2026-10-06 20:31 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  2. 2026-10-06 20:15 UTCEG score recompute
  3. 2026-10-06 20:11 UTCNVD update
  4. 2026-10-06 19:53 UTCEG score recompute
  5. 2026-10-06 19:51 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  6. 2026-10-06 19:31 UTCNVD update
  7. 2026-10-06 19:00 UTCEG score recomputeFirst assessed: 8.8 HIGH
  8. 2026-10-06 18:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-106357?
CVE-2026-106357 is a high-severity vulnerability; its CVE record was published on October 6, 2026. Use after free in WebRTC in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
When was the CVE record for CVE-2026-106357 published?
The CVE record for CVE-2026-106357 was published on October 6, 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 7, 2026; the record at its source may have been updated since.
Is CVE-2026-106357 actively exploited?
CVE-2026-106357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106357?
CVE-2026-106357 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-106357?
No fix for CVE-2026-106357 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-106357 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-106357

Explore →

Is Your Infrastructure Affected by CVE-2026-106357?

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

Book a Demo →Browse All CVEs