Inappropriate implementation in Skia in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
CVE-2026-9892
Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-05-29. NVD baseline CVSS 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
- CRITICALper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Critical)
- EG Score
- 8.3(medium)
- EG Risk
- 37(Track)EG Risk 37/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%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
May 28, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jun 3, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.htmlVendor Advisories for CVE-2026-9892(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(5 across 4 ecosystems)
Debian:14(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 148.0.7778.96-3 (126 versions) | 148.0.7778.215-1 | — |
| libskia | 146.20260311+dfsg-1 ... 146.20260414~git.ef5f213+dfsg-4 (8 versions) | 146.20260414~git.ef5f213+dfsg-5 | — |
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 ... 148.0.7778.96-3 (359 versions) | 148.0.7778.215-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 148.0.7778.96-3 (125 versions) | 148.0.7778.215-1~deb13u1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 110× 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 300 total refreshes for this CVE.
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 04:33 UTCEG score recompute
- 2026-08-25 04:33 UTCGHSA enrichment
- 2026-08-24 14:18 UTCEPSS rescore
- 2026-08-23 14:24 UTCEG score recompute
- 2026-08-23 14:24 UTCVendor advisory
- 2026-08-23 14:24 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 15:18 UTCGHSA enrichment
- 2026-08-20 21:46 UTCVendor advisory
- 2026-08-20 21:46 UTCGHSA enrichment
- 2026-08-20 10:38 UTCEG score recompute
- 2026-08-20 10:38 UTCVendor advisory
- 2026-08-20 10:38 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:59 UTCVendor advisory
- 2026-08-17 06:59 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-16 15:08 UTCEG score recompute
- 2026-08-16 15:08 UTCVendor advisory
- 2026-08-16 15:08 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:29 UTCEG score recompute
- 2026-08-16 02:29 UTCVendor advisory
- 2026-08-16 02:29 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 22:55 UTCVendor advisory
- 2026-08-14 22:55 UTCGHSA enrichment
- 2026-08-14 11:51 UTCVendor advisory
- 2026-08-14 11:51 UTCGHSA enrichment
- 2026-08-14 00:47 UTCEG score recompute
- 2026-08-14 00:47 UTCVendor advisory
- 2026-08-14 00:47 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 08:01 UTCVendor advisory
- 2026-08-13 08:01 UTCGHSA enrichment
- 2026-08-12 20:33 UTCEG score recompute
- 2026-08-12 20:33 UTCVendor advisory
- 2026-08-12 20:33 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 09:29 UTCVendor advisory
- 2026-08-12 09:29 UTCGHSA enrichment
- 2026-08-11 22:24 UTCEG score recompute
- 2026-08-11 22:24 UTCVendor advisory
- 2026-08-11 22:24 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 11:13 UTCVendor advisory
- 2026-08-11 11:13 UTCGHSA enrichment
- 2026-08-11 00:02 UTCEG score recompute
- 2026-08-11 00:02 UTCVendor advisory
- 2026-08-11 00:02 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 12:37 UTCVendor advisory
- 2026-08-10 12:37 UTCGHSA enrichment
- 2026-08-10 01:23 UTCVendor advisory
- 2026-08-10 01:23 UTCGHSA enrichment
- 2026-08-09 14:18 UTCEG score recompute
- 2026-08-09 14:18 UTCVendor advisory
- 2026-08-09 14:18 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 03:14 UTCEG score recompute
- 2026-08-09 03:14 UTCVendor advisory
- 2026-08-09 03:14 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 16:10 UTCVendor advisory
- 2026-08-08 16:10 UTCGHSA enrichment
- 2026-08-08 04:10 UTCGHSA enrichment
- 2026-08-07 17:06 UTCEG score recompute
- 2026-08-07 17:06 UTCVendor advisory
- 2026-08-07 17:06 UTCGHSA enrichment
- 2026-08-07 16:30 UTCEPSS rescore
- 2026-08-07 06:01 UTCVendor advisory
- 2026-08-07 06:01 UTCGHSA enrichment
- 2026-08-06 18:55 UTCEG score recompute
- 2026-08-06 18:55 UTCVendor advisory
- 2026-08-06 18:55 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 07:51 UTCVendor advisory
- 2026-08-06 07:50 UTCGHSA enrichment
- 2026-08-05 20:46 UTCEG score recompute
- 2026-08-05 20:46 UTCVendor advisory
- 2026-08-05 20:46 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 23:31 UTCEG score recompute
- 2026-08-04 23:31 UTCVendor advisory
- 2026-08-04 23:31 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 03:13 UTCVendor advisory
- 2026-08-04 03:13 UTCGHSA enrichment
- 2026-08-03 16:02 UTCEG score recompute
- 2026-08-03 16:02 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-9892?
When was CVE-2026-9892 disclosed?
Is CVE-2026-9892 actively exploited?
What is the CVSS score of CVE-2026-9892?
How do I remediate CVE-2026-9892?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9892
Is Your Infrastructure Affected by CVE-2026-9892?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.