Heap buffer overflow in Chromecast in Google Chrome on Android, Linux, ChromeOS prior to 148.0.7778.179 allowed a local attacker to execute arbitrary code inside a sandbox via malicious network traffic. (Chromium security severity: Medium)
CVE-2026-9123
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 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
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- 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
- 8%
- KEV
- Not listed
Published
May 20, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jun 5, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0841193308.htmlVendor Advisories for CVE-2026-9123(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 ... 148.0.7778.96-3 (356 versions) | 148.0.7778.178-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 148.0.7778.96-3 (122 versions) | 148.0.7778.178-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 148.0.7778.96-3 (123 versions) | 148.0.7778.178-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 85× 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 261 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 16:52 UTCEG score recompute
- 2026-08-23 16:52 UTCVendor advisory
- 2026-08-23 16:52 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 22:52 UTCEG score recompute
- 2026-08-21 22:52 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 18:53 UTCEG score recompute
- 2026-08-20 18:53 UTCVendor advisory
- 2026-08-20 18:53 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-17 09:51 UTCVendor advisory
- 2026-08-17 09:51 UTCGHSA enrichment
- 2026-08-16 16:52 UTCEG score recompute
- 2026-08-16 16:52 UTCVendor advisory
- 2026-08-16 16:52 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 03:28 UTCEG score recompute
- 2026-08-16 03:28 UTCVendor advisory
- 2026-08-16 03:28 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:33 UTCEG score recompute
- 2026-08-15 01:33 UTCVendor advisory
- 2026-08-15 01:33 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 13:47 UTCVendor advisory
- 2026-08-14 13:47 UTCGHSA enrichment
- 2026-08-14 02:00 UTCEG score recompute
- 2026-08-14 02:00 UTCVendor advisory
- 2026-08-14 02:00 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 02:01 UTCGHSA enrichment
- 2026-08-12 14:14 UTCEG score recompute
- 2026-08-12 14:14 UTCVendor advisory
- 2026-08-12 14:14 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 01:38 UTCVendor advisory
- 2026-08-12 01:38 UTCGHSA enrichment
- 2026-08-11 13:50 UTCEG score recompute
- 2026-08-11 13:50 UTCVendor advisory
- 2026-08-11 13:50 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 00:37 UTCEG score recompute
- 2026-08-11 00:37 UTCVendor advisory
- 2026-08-11 00:37 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 12:50 UTCGHSA enrichment
- 2026-08-10 01:04 UTCEG score recompute
- 2026-08-10 01:04 UTCVendor advisory
- 2026-08-10 01:04 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 13:17 UTCVendor advisory
- 2026-08-09 13:17 UTCGHSA enrichment
- 2026-08-09 01:30 UTCEG score recompute
- 2026-08-09 01:30 UTCVendor advisory
- 2026-08-09 01:30 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 08:11 UTCVendor advisory
- 2026-08-08 08:11 UTCGHSA enrichment
- 2026-08-07 20:24 UTCEG score recompute
- 2026-08-07 20:24 UTCGHSA enrichment
- 2026-08-07 16:30 UTCEPSS rescore
- 2026-08-07 08:37 UTCVendor advisory
- 2026-08-07 08:37 UTCGHSA enrichment
- 2026-08-06 20:49 UTCEG score recompute
- 2026-08-06 20:49 UTCVendor advisory
- 2026-08-06 20:49 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 09:02 UTCVendor advisory
- 2026-08-06 09:02 UTCGHSA enrichment
- 2026-08-05 21:15 UTCEG score recompute
- 2026-08-05 21:15 UTCVendor advisory
- 2026-08-05 21:15 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 04:40 UTCGHSA enrichment
- 2026-08-03 16:53 UTCEG score recompute
- 2026-08-03 16:53 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 05:01 UTCVendor advisory
- 2026-08-03 05:01 UTCGHSA enrichment
- 2026-08-02 17:12 UTCVendor advisory
- 2026-08-02 17:12 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-9123?
When was CVE-2026-9123 disclosed?
Is CVE-2026-9123 actively exploited?
What is the CVSS score of CVE-2026-9123?
How do I remediate CVE-2026-9123?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9123
Is Your Infrastructure Affected by CVE-2026-9123?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.