Use after free in Core in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
CVE-2026-15773
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-14. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.6; 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
- 9.6
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 9.6(medium)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity96% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (2)
Auto-updated Aug 23, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0353146366.htmlVendor Advisories for CVE-2026-15773(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 (387 versions) | 150.0.7871.124-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (153 versions) | 150.0.7871.124-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (154 versions) | 150.0.7871.124-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 59× in last 7d / 349× 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 436 total refreshes for this CVE.
- 2026-08-30 08:14 UTCVendor advisory
- 2026-08-30 08:14 UTCGHSA enrichment
- 2026-08-30 04:09 UTCEG score recompute
- 2026-08-30 04:09 UTCVendor advisory
- 2026-08-30 04:09 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 01:53 UTCVendor advisory
- 2026-08-28 01:53 UTCGHSA enrichment
- 2026-08-27 21:28 UTCEG score recompute
- 2026-08-27 21:28 UTCVendor advisory
- 2026-08-27 21:28 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 12:53 UTCVendor advisory
- 2026-08-27 12:53 UTCGHSA enrichment
- 2026-08-27 03:17 UTCVendor advisory
- 2026-08-27 03:17 UTCGHSA enrichment
- 2026-08-26 23:18 UTCEG score recompute
- 2026-08-26 23:18 UTCVendor advisory
- 2026-08-26 23:18 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 12:11 UTCVendor advisory
- 2026-08-26 12:11 UTCGHSA enrichment
- 2026-08-26 05:56 UTCVendor advisory
- 2026-08-26 05:56 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-26 01:15 UTCVendor advisory
- 2026-08-26 01:15 UTCGHSA enrichment
- 2026-08-25 21:09 UTCVendor advisory
- 2026-08-25 21:09 UTCGHSA enrichment
- 2026-08-25 15:45 UTCEG score recompute
- 2026-08-25 15:45 UTCVendor advisory
- 2026-08-25 15:45 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 11:33 UTCVendor advisory
- 2026-08-25 11:33 UTCGHSA enrichment
- 2026-08-25 07:34 UTCVendor advisory
- 2026-08-25 07:33 UTCGHSA enrichment
- 2026-08-25 03:34 UTCVendor advisory
- 2026-08-25 03:34 UTCGHSA enrichment
- 2026-08-24 23:37 UTCVendor advisory
- 2026-08-24 23:37 UTCGHSA enrichment
- 2026-08-24 19:38 UTCEG score recompute
- 2026-08-24 19:38 UTCVendor advisory
- 2026-08-24 19:38 UTCGHSA enrichment
- 2026-08-24 12:19 UTCEG score recompute
- 2026-08-24 12:19 UTCVendor advisory
- 2026-08-24 12:19 UTCGHSA enrichment
- 2026-08-24 08:09 UTCVendor advisory
- 2026-08-24 08:09 UTCGHSA enrichment
- 2026-08-24 04:11 UTCVendor advisory
- 2026-08-24 04:11 UTCGHSA enrichment
- 2026-08-24 00:14 UTCVendor advisory
- 2026-08-24 00:13 UTCGHSA enrichment
- 2026-08-23 20:16 UTCVendor advisory
- 2026-08-23 20:16 UTCGHSA enrichment
- 2026-08-23 16:18 UTCVendor advisory
- 2026-08-23 16:18 UTCGHSA enrichment
- 2026-08-23 12:15 UTCVendor advisory
- 2026-08-23 12:15 UTCGHSA enrichment
- 2026-08-23 08:16 UTCVendor advisory
- 2026-08-23 08:16 UTCGHSA enrichment
- 2026-08-23 04:19 UTCVendor advisory
- 2026-08-23 04:19 UTCGHSA enrichment
- 2026-08-23 00:21 UTCEG score recompute
- 2026-08-23 00:21 UTCVendor advisory
- 2026-08-23 00:21 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 20:17 UTCVendor advisory
- 2026-08-22 20:17 UTCGHSA enrichment
- 2026-08-22 16:19 UTCVendor advisory
- 2026-08-22 16:19 UTCGHSA enrichment
- 2026-08-22 12:17 UTCVendor advisory
- 2026-08-22 12:17 UTCGHSA enrichment
- 2026-08-22 07:56 UTCVendor advisory
- 2026-08-22 07:56 UTCGHSA enrichment
- 2026-08-22 03:58 UTCVendor advisory
- 2026-08-22 03:58 UTCGHSA enrichment
- 2026-08-22 00:00 UTCEG score recompute
- 2026-08-22 00:00 UTCVendor advisory
- 2026-08-22 00:00 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 20:01 UTCGHSA enrichment
- 2026-08-21 16:03 UTCGHSA enrichment
- 2026-08-21 12:06 UTCVendor advisory
- 2026-08-21 12:06 UTCGHSA enrichment
- 2026-08-21 08:06 UTCVendor advisory
- 2026-08-21 08:06 UTCGHSA enrichment
- 2026-08-21 04:08 UTCVendor advisory
- 2026-08-21 04:08 UTCGHSA enrichment
- 2026-08-21 00:11 UTCEG score recompute
- 2026-08-21 00:11 UTCVendor advisory
- 2026-08-21 00:11 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 20:13 UTCVendor advisory
- 2026-08-20 20:13 UTCGHSA enrichment
- 2026-08-20 16:16 UTCVendor advisory
- 2026-08-20 16:16 UTCGHSA enrichment
- 2026-08-20 12:18 UTCVendor advisory
- 2026-08-20 12:18 UTCGHSA enrichment
- 2026-08-20 08:21 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Frequently asked(5)
What is CVE-2026-15773?
When was CVE-2026-15773 disclosed?
Is CVE-2026-15773 actively exploited?
What is the CVSS score of CVE-2026-15773?
How do I remediate CVE-2026-15773?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15773
Is Your Infrastructure Affected by CVE-2026-15773?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.