Heap buffer overflow in Codecs in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted video file. (Chromium security severity: High)
CVE-2026-8529
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-14. NVD baseline CVSS 8.8; 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.8
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 8.8(medium)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
May 14, 2026
Last Modified
May 18, 2026
Advisory Details (2)
Auto-updated May 14, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.htmlVendor Advisories for CVE-2026-8529(1)
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 ... 148.0.7778.96-3 (353 versions) | 148.0.7778.167-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 148.0.7778.96-3 (119 versions) | 148.0.7778.167-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 148.0.7778.96-3 (120 versions) | 148.0.7778.167-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 83× 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 262 total refreshes for this CVE.
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 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-24 14:18 UTCEPSS rescore
- 2026-08-23 17:36 UTCEG score recompute
- 2026-08-23 17:36 UTCVendor advisory
- 2026-08-23 17:36 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 01:43 UTCEG score recompute
- 2026-08-22 01:43 UTCVendor advisory
- 2026-08-22 01:43 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 19:32 UTCEG score recompute
- 2026-08-20 19:32 UTCVendor advisory
- 2026-08-20 19:32 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:21 UTCEG score recompute
- 2026-08-17 10:21 UTCVendor advisory
- 2026-08-17 10:21 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 03:54 UTCEG score recompute
- 2026-08-16 03:54 UTCVendor advisory
- 2026-08-16 03:54 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-15 00:16 UTCVendor advisory
- 2026-08-15 00:16 UTCGHSA enrichment
- 2026-08-14 13:19 UTCVendor advisory
- 2026-08-14 13:19 UTCGHSA enrichment
- 2026-08-14 02:23 UTCEG score recompute
- 2026-08-14 02:23 UTCVendor advisory
- 2026-08-14 02:23 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:54 UTCGHSA enrichment
- 2026-08-12 14:57 UTCEG score recompute
- 2026-08-12 14:57 UTCVendor advisory
- 2026-08-12 14:57 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 02:20 UTCVendor advisory
- 2026-08-12 02:20 UTCGHSA enrichment
- 2026-08-11 15:24 UTCEG score recompute
- 2026-08-11 15:24 UTCVendor advisory
- 2026-08-11 15:23 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 00:50 UTCEG score recompute
- 2026-08-11 00:50 UTCVendor advisory
- 2026-08-11 00:50 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 11:28 UTCGHSA enrichment
- 2026-08-09 23:41 UTCEG score recompute
- 2026-08-09 23:41 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 12:45 UTCVendor advisory
- 2026-08-09 12:45 UTCGHSA enrichment
- 2026-08-09 01:48 UTCEG score recompute
- 2026-08-09 01:48 UTCVendor advisory
- 2026-08-09 01:48 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 04:23 UTCGHSA enrichment
- 2026-08-07 17:27 UTCEG score recompute
- 2026-08-07 17:27 UTCVendor advisory
- 2026-08-07 17:27 UTCGHSA enrichment
- 2026-08-07 16:30 UTCEPSS rescore
- 2026-08-07 06:30 UTCVendor advisory
- 2026-08-07 06:30 UTCGHSA enrichment
- 2026-08-06 19:27 UTCEG score recompute
- 2026-08-06 19:27 UTCVendor advisory
- 2026-08-06 19:27 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 08:31 UTCVendor advisory
- 2026-08-06 08:31 UTCGHSA enrichment
- 2026-08-05 21:35 UTCEG score recompute
- 2026-08-05 21:35 UTCVendor advisory
- 2026-08-05 21:35 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 05:55 UTCVendor advisory
- 2026-08-04 05:55 UTCGHSA enrichment
- 2026-08-03 18:59 UTCEG score recompute
- 2026-08-03 18:59 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 18:36 UTCVendor advisory
- 2026-08-02 18:36 UTCGHSA enrichment
- 2026-08-02 07:40 UTCVendor advisory
- 2026-08-02 07:40 UTCGHSA enrichment
- 2026-08-01 19:11 UTCEG score recompute
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-8529?
When was CVE-2026-8529 disclosed?
Is CVE-2026-8529 actively exploited?
What is the CVSS score of CVE-2026-8529?
How do I remediate CVE-2026-8529?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-8529
Is Your Infrastructure Affected by CVE-2026-8529?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.