Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.128 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
CVE-2026-15904
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 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
July 20, 2026
Last Modified
July 24, 2026
Advisory Details (2)
Auto-updated Jul 22, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_049796704.htmlVendor Advisories for CVE-2026-15904(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 ... 150.0.7871.46-1~deb13u1 (390 versions) | 150.0.7871.181-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (156 versions) | 150.0.7871.181-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (157 versions) | 150.0.7871.181-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 29× in last 7d / 163× 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 1,265 total refreshes for this CVE.
- 2026-08-30 02:28 UTCEG score recompute
- 2026-08-30 02:28 UTCVendor advisory
- 2026-08-30 02:28 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 22:57 UTCEG score recompute
- 2026-08-27 22:57 UTCVendor advisory
- 2026-08-27 22:57 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 11:33 UTCVendor advisory
- 2026-08-27 11:33 UTCGHSA enrichment
- 2026-08-26 21:41 UTCEG score recompute
- 2026-08-26 21:41 UTCVendor advisory
- 2026-08-26 21:41 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 05:48 UTCVendor advisory
- 2026-08-26 05:47 UTCGHSA enrichment
- 2026-08-25 18:23 UTCEG score recompute
- 2026-08-25 18:23 UTCVendor advisory
- 2026-08-25 18:23 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 06:18 UTCGHSA enrichment
- 2026-08-24 18:55 UTCEG score recompute
- 2026-08-24 18:55 UTCVendor advisory
- 2026-08-24 18:55 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-24 05:21 UTCVendor advisory
- 2026-08-24 05:21 UTCGHSA enrichment
- 2026-08-23 17:57 UTCVendor advisory
- 2026-08-23 17:57 UTCGHSA enrichment
- 2026-08-23 06:34 UTCEG score recompute
- 2026-08-23 06:34 UTCVendor advisory
- 2026-08-23 06:34 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 19:10 UTCVendor advisory
- 2026-08-22 19:10 UTCGHSA enrichment
- 2026-08-22 07:46 UTCEG score recompute
- 2026-08-22 07:46 UTCVendor advisory
- 2026-08-22 07:46 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 20:22 UTCGHSA enrichment
- 2026-08-21 08:59 UTCEG score recompute
- 2026-08-21 08:59 UTCVendor advisory
- 2026-08-21 08:59 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:33 UTCVendor advisory
- 2026-08-20 21:33 UTCGHSA enrichment
- 2026-08-20 10:09 UTCEG score recompute
- 2026-08-20 10:09 UTCVendor advisory
- 2026-08-20 10:09 UTCGHSA enrichment
- 2026-08-19 22:46 UTCEG score recompute
- 2026-08-19 22:46 UTCVendor advisory
- 2026-08-19 22:46 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 06:59 UTCVendor advisory
- 2026-08-19 06:59 UTCGHSA enrichment
- 2026-08-18 19:35 UTCEG score recompute
- 2026-08-18 19:35 UTCVendor advisory
- 2026-08-18 19:35 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 01:44 UTCVendor advisory
- 2026-08-18 01:44 UTCGHSA enrichment
- 2026-08-17 14:08 UTCEG score recompute
- 2026-08-17 14:08 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 02:45 UTCVendor advisory
- 2026-08-17 02:45 UTCGHSA enrichment
- 2026-08-16 15:21 UTCEG score recompute
- 2026-08-16 15:21 UTCVendor advisory
- 2026-08-16 15:21 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 03:58 UTCEG score recompute
- 2026-08-16 03:58 UTCVendor advisory
- 2026-08-16 03:58 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 16:35 UTCVendor advisory
- 2026-08-15 16:35 UTCGHSA enrichment
- 2026-08-15 05:11 UTCEG score recompute
- 2026-08-15 05:11 UTCVendor advisory
- 2026-08-15 05:11 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:47 UTCVendor advisory
- 2026-08-14 17:47 UTCGHSA enrichment
- 2026-08-14 06:24 UTCEG score recompute
- 2026-08-14 06:24 UTCVendor advisory
- 2026-08-14 06:24 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 19:00 UTCVendor advisory
- 2026-08-13 19:00 UTCGHSA enrichment
- 2026-08-13 07:37 UTCVendor advisory
- 2026-08-13 07:37 UTCGHSA enrichment
- 2026-08-12 20:13 UTCEG score recompute
- 2026-08-12 20:13 UTCVendor advisory
- 2026-08-12 20:13 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 08:50 UTCVendor advisory
- 2026-08-12 08:50 UTCGHSA enrichment
- 2026-08-11 21:27 UTCEG score recompute
- 2026-08-11 21:27 UTCVendor advisory
- 2026-08-11 21:27 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Frequently asked(5)
What is CVE-2026-15904?
When was CVE-2026-15904 disclosed?
Is CVE-2026-15904 actively exploited?
What is the CVSS score of CVE-2026-15904?
How do I remediate CVE-2026-15904?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15904
Is Your Infrastructure Affected by CVE-2026-15904?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.