Improper input validation in GPU in Google Chrome on on Android prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
CVE-2026-79008
Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- Vendor severity
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- EG Score
- 8.3(high)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity83% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 41%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 27, 2026
Advisory Details (2)
Auto-updated Aug 26, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.htmlVendor Advisories for CVE-2026-79008(1)
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 24× in last 7d / 24× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 21:04 UTCGHSA enrichment
- 2026-08-29 08:21 UTCEG score recompute
- 2026-08-29 08:21 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:36 UTCGHSA enrichment
- 2026-08-28 06:50 UTCGHSA enrichment
- 2026-08-27 18:07 UTCEG score recompute
- 2026-08-27 18:07 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 04:27 UTCGHSA enrichment
- 2026-08-27 04:05 UTCGHSA enrichment
- 2026-08-26 19:01 UTCEG score recompute
- 2026-08-26 19:01 UTCGHSA enrichment
- 2026-08-26 16:40 UTCGHSA enrichment
- 2026-08-26 15:43 UTCEG score recompute
- 2026-08-26 15:43 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 14:45 UTCEG score recompute▲ 1.80
- 2026-08-26 14:45 UTCGHSA enrichment
- 2026-08-26 14:41 UTCMITRE cvelistV5CVSS v3 → 8.3 · severity → HIGH
- 2026-08-25 21:26 UTCNVD update
- 2026-08-25 20:29 UTCEG score recompute
- 2026-08-25 20:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-79008?
When was CVE-2026-79008 disclosed?
Is CVE-2026-79008 actively exploited?
What is the CVSS score of CVE-2026-79008?
How do I remediate CVE-2026-79008?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-79008
Is Your Infrastructure Affected by CVE-2026-79008?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.