Out of bounds read in Extensions in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
CVE-2026-113010
MEDIUMPre-NVD 6.56.5Trending — 5 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.5 from GitHub Security Advisory published 2026-10-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Also known asEUVD-2026-105588 (ENISA EUVD) · GHSA-hgjv-7h3r-h789 (GitHub Security Advisories)Source: ENISA EUVD
6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.5
- Vendor severity
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- EG Score
- 6.5MEDIUMhigh confidence
- EG Risk
- 45EG Risk 45/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)Severity65% × 45%Impact severity (EG Severity): CVSS 6.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.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 public PoC (CISA Vulnrichment) · Automatable no (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. - EPSS PROB
- 0.3%
- EPSS %ILE
- 21st
- 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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 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 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 20, 2026
Last Modified
October 21, 2026
Advisory Details (2)
Auto-updated Oct 25, 2026Patch available.
Web page
Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.htmlVendor Advisories for CVE-2026-113010(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 23× 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.
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-25 14:51 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-21 20:25 UTCGHSA enrichmentGHSA-hgjv-7h3r-h789 · GitHub CVSS 6.5
- 2026-10-21 19:26 UTCEG score recompute
- 2026-10-21 19:25 UTCGHSA enrichmentGHSA-hgjv-7h3r-h789 · GitHub CVSS 6.5
- 2026-10-21 19:21 UTCEG score recompute
- 2026-10-21 19:21 UTCGHSA enrichmentGHSA-hgjv-7h3r-h789 · GitHub CVSS 6.5
- 2026-10-21 17:46 UTCEG score recompute
- 2026-10-21 17:46 UTCGHSA enrichmentGHSA-hgjv-7h3r-h789
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-21 16:31 UTCGHSA enrichmentGHSA-hgjv-7h3r-h789
- 2026-10-21 15:51 UTCEG score recompute
- 2026-10-21 15:51 UTCGHSA enrichmentGHSA-hgjv-7h3r-h789
- 2026-10-21 15:50 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
- 2026-10-21 14:48 UTCGHSA enrichmentGHSA-hgjv-7h3r-h789
- 2026-10-20 22:25 UTCNVD update
- 2026-10-20 21:19 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
- 2026-10-20 21:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-113010?
CVE-2026-113010 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. Out of bounds read in Extensions in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
When was the CVE record for CVE-2026-113010 published?
The CVE record for CVE-2026-113010 was published on October 20, 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 21, 2026; the record at its source may have been updated since.
Is CVE-2026-113010 actively exploited?
CVE-2026-113010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-113010?
CVE-2026-113010 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-113010?
A fix for CVE-2026-113010 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-113010 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-113010
Is Your Infrastructure Affected by CVE-2026-113010?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.