Out of bounds write in GPU in Google Chrome on Android prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
CVE-2026-12030
Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-12. 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
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 8.3(medium)
- EG Risk
- 42(Track)EG Risk 42/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%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
June 11, 2026
Last Modified
June 12, 2026
Advisory Details (2)
Auto-updated Jun 12, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01962725236.htmlVendor Advisories for CVE-2026-12030(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 113.0.5672.126-1 ... 149.0.7827.53-1~deb13u1 (369 versions) | 149.0.7827.114-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (135 versions) | 149.0.7827.114-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (136 versions) | 149.0.7827.114-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 47× 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.
Showing the most recent 100 of 309 total refreshes for this CVE.
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-14 04:06 UTCEG score recompute
- 2026-09-14 04:06 UTCVendor advisory
- 2026-09-14 04:06 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-08-30 23:49 UTCEG score recompute
- 2026-08-30 23:49 UTCVendor advisory
- 2026-08-30 23:49 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 23:52 UTCEG score recompute
- 2026-08-24 23:52 UTCVendor advisory
- 2026-08-24 23:52 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-23 23:23 UTCVendor advisory
- 2026-08-23 23:23 UTCGHSA enrichment
- 2026-08-23 10:39 UTCEG score recompute
- 2026-08-23 10:39 UTCVendor advisory
- 2026-08-23 10:39 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 22:43 UTCGHSA enrichment
- 2026-08-21 09:55 UTCEG score recompute
- 2026-08-21 09:55 UTCVendor advisory
- 2026-08-21 09:55 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:11 UTCVendor advisory
- 2026-08-20 21:11 UTCGHSA enrichment
- 2026-08-20 08:49 UTCEG score recompute
- 2026-08-20 08:49 UTCVendor advisory
- 2026-08-20 08:49 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 13:47 UTCEG score recompute
- 2026-08-19 13:47 UTCVendor advisory
- 2026-08-19 13:46 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 03:54 UTCVendor advisory
- 2026-08-17 03:54 UTCGHSA enrichment
- 2026-08-16 15:32 UTCEG score recompute
- 2026-08-16 15:32 UTCVendor advisory
- 2026-08-16 15:32 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 03:11 UTCEG score recompute
- 2026-08-16 03:11 UTCVendor advisory
- 2026-08-16 03:11 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 14:50 UTCVendor advisory
- 2026-08-15 14:50 UTCGHSA enrichment
- 2026-08-15 02:28 UTCEG score recompute
- 2026-08-15 02:28 UTCVendor advisory
- 2026-08-15 02:28 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 14:07 UTCVendor advisory
- 2026-08-14 14:07 UTCGHSA enrichment
- 2026-08-14 01:46 UTCEG score recompute
- 2026-08-14 01:46 UTCVendor advisory
- 2026-08-14 01:46 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 13:24 UTCVendor advisory
- 2026-08-13 13:24 UTCGHSA enrichment
- 2026-08-13 00:55 UTCEG score recompute
- 2026-08-13 00:55 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 12:34 UTCVendor advisory
- 2026-08-12 12:34 UTCGHSA enrichment
- 2026-08-12 00:13 UTCEG score recompute
- 2026-08-12 00:13 UTCVendor advisory
- 2026-08-12 00:13 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 11:51 UTCEG score recompute
- 2026-08-11 11:51 UTCVendor advisory
- 2026-08-11 11:51 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 23:30 UTCGHSA enrichment
- 2026-08-10 11:09 UTCGHSA enrichment
- 2026-08-09 22:47 UTCEG score recompute
- 2026-08-09 22:47 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 10:26 UTCVendor advisory
- 2026-08-09 10:26 UTCGHSA enrichment
- 2026-08-08 22:05 UTCEG score recompute
- 2026-08-08 22:05 UTCVendor advisory
- 2026-08-08 22:05 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 09:44 UTCVendor advisory
- 2026-08-08 09:44 UTCGHSA enrichment
- 2026-08-07 21:23 UTCEG score recompute
- 2026-08-07 21:23 UTCVendor advisory
- 2026-08-07 21:23 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-122
- CVE-2016-9603NVD 5.5EG 9.9EPSS p91CRITICAL
- CVE-2017-20241EG 9.8CRITICAL
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2006-10002NVD 7.5EG 9.8CRITICAL
- CVE-2019-18296EG 9.8EPSS p92CRITICAL
- CVE-2019-18295EG 9.8EPSS p92CRITICAL
- CVE-2019-18293EG 9.8EPSS p92CRITICAL
- CVE-2019-18289EG 9.8EPSS p92CRITICAL
- CVE-2019-14901EG 9.8EPSS p97CRITICAL
- CVE-2019-14895EG 9.8EPSS p94CRITICAL
Frequently asked(5)
What is CVE-2026-12030?
When was CVE-2026-12030 disclosed?
Is CVE-2026-12030 actively exploited?
What is the CVSS score of CVE-2026-12030?
How do I remediate CVE-2026-12030?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12030
Is Your Infrastructure Affected by CVE-2026-12030?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.