Integer overflow in Skia in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
CVE-2026-10009
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-29. NVD baseline CVSS 7.5; 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
- 7.5
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 7.5(medium)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
May 28, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jun 7, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.htmlVendor Advisories for CVE-2026-10009(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 6× in last 7d / 84× 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 313 total refreshes for this CVE.
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 04:30 UTCEG score recompute
- 2026-08-25 04:30 UTCGHSA enrichment
- 2026-08-23 14:21 UTCEG score recompute
- 2026-08-23 14:21 UTCVendor advisory
- 2026-08-23 14:21 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 15:15 UTCEG score recompute
- 2026-08-21 15:15 UTCVendor advisory
- 2026-08-21 15:15 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:29 UTCVendor advisory
- 2026-08-20 22:29 UTCGHSA enrichment
- 2026-08-20 10:31 UTCEG score recompute
- 2026-08-20 10:31 UTCVendor advisory
- 2026-08-20 10:31 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 06:56 UTCVendor advisory
- 2026-08-17 06:56 UTCGHSA enrichment
- 2026-08-16 15:06 UTCEG score recompute
- 2026-08-16 15:06 UTCVendor advisory
- 2026-08-16 15:06 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:27 UTCEG score recompute
- 2026-08-16 02:27 UTCVendor advisory
- 2026-08-16 02:27 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 00:23 UTCVendor advisory
- 2026-08-15 00:23 UTCGHSA enrichment
- 2026-08-14 12:33 UTCVendor advisory
- 2026-08-14 12:33 UTCGHSA enrichment
- 2026-08-14 00:44 UTCEG score recompute
- 2026-08-14 00:44 UTCVendor advisory
- 2026-08-14 00:44 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 11:17 UTCVendor advisory
- 2026-08-13 11:17 UTCGHSA enrichment
- 2026-08-12 23:27 UTCEG score recompute
- 2026-08-12 23:27 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 11:38 UTCVendor advisory
- 2026-08-12 11:38 UTCGHSA enrichment
- 2026-08-11 23:47 UTCEG score recompute
- 2026-08-11 23:47 UTCVendor advisory
- 2026-08-11 23:47 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 11:57 UTCEG score recompute
- 2026-08-11 11:57 UTCVendor advisory
- 2026-08-11 11:57 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 23:59 UTCVendor advisory
- 2026-08-10 23:59 UTCGHSA enrichment
- 2026-08-10 07:46 UTCGHSA enrichment
- 2026-08-09 19:56 UTCEG score recompute
- 2026-08-09 19:56 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:07 UTCGHSA enrichment
- 2026-08-08 20:17 UTCEG score recompute
- 2026-08-08 20:17 UTCVendor advisory
- 2026-08-08 20:17 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 07:53 UTCGHSA enrichment
- 2026-08-07 20:04 UTCEG score recompute
- 2026-08-07 20:04 UTCVendor advisory
- 2026-08-07 20:04 UTCGHSA enrichment
- 2026-08-07 08:14 UTCVendor advisory
- 2026-08-07 08:14 UTCGHSA enrichment
- 2026-08-06 20:24 UTCEG score recompute
- 2026-08-06 20:24 UTCVendor advisory
- 2026-08-06 20:24 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 08:34 UTCVendor advisory
- 2026-08-06 08:34 UTCGHSA enrichment
- 2026-08-05 20:44 UTCEG score recompute
- 2026-08-05 20:44 UTCVendor advisory
- 2026-08-05 20:44 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 23:24 UTCEG score recompute
- 2026-08-04 23:24 UTCVendor advisory
- 2026-08-04 23:24 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 03:49 UTCGHSA enrichment
- 2026-08-03 15:59 UTCEG score recompute
- 2026-08-03 15:59 UTCVendor advisory
- 2026-08-03 15:59 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-03 01:40 UTCVendor advisory
- 2026-08-03 01:40 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-10009?
When was CVE-2026-10009 disclosed?
Is CVE-2026-10009 actively exploited?
What is the CVSS score of CVE-2026-10009?
How do I remediate CVE-2026-10009?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10009
Is Your Infrastructure Affected by CVE-2026-10009?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.