Inappropriate implementation in Tint in Google Chrome on Mac prior to 151.0.7922.72 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)
CVE-2026-18015
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-30. 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
- LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
- EG Score
- 9.6(high)
- 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
- 10%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
August 4, 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_0887107924.htmlVendor Advisories for CVE-2026-18015(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 ... 151.0.7922.47-1 (394 versions) | 151.0.7922.71-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 151.0.7922.71-1~deb12u1 (160 versions) | 151.0.7922.71-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (162 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 81× in last 7d / 322× 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 322 total refreshes for this CVE.
- 2026-08-26 08:43 UTCVendor advisory
- 2026-08-26 08:43 UTCGHSA enrichment
- 2026-08-26 04:25 UTCVendor advisory
- 2026-08-26 04:25 UTCGHSA enrichment
- 2026-08-25 23:57 UTCVendor advisory
- 2026-08-25 23:57 UTCGHSA enrichment
- 2026-08-25 19:39 UTCVendor advisory
- 2026-08-25 19:39 UTCGHSA enrichment
- 2026-08-25 15:20 UTCVendor advisory
- 2026-08-25 15:20 UTCGHSA enrichment
- 2026-08-25 11:03 UTCVendor advisory
- 2026-08-25 11:03 UTCGHSA enrichment
- 2026-08-25 06:45 UTCGHSA enrichment
- 2026-08-25 02:27 UTCVendor advisory
- 2026-08-25 02:27 UTCGHSA enrichment
- 2026-08-24 22:10 UTCVendor advisory
- 2026-08-24 22:10 UTCGHSA enrichment
- 2026-08-24 17:50 UTCEG score recompute
- 2026-08-24 17:50 UTCVendor advisory
- 2026-08-24 17:50 UTCGHSA enrichment
- 2026-08-24 12:03 UTCEG score recompute
- 2026-08-24 12:03 UTCVendor advisory
- 2026-08-24 12:03 UTCGHSA enrichment
- 2026-08-24 07:30 UTCVendor advisory
- 2026-08-24 07:30 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-24 03:09 UTCVendor advisory
- 2026-08-24 03:09 UTCGHSA enrichment
- 2026-08-23 22:21 UTCVendor advisory
- 2026-08-23 22:21 UTCGHSA enrichment
- 2026-08-23 18:03 UTCVendor advisory
- 2026-08-23 18:03 UTCGHSA enrichment
- 2026-08-23 13:45 UTCVendor advisory
- 2026-08-23 13:45 UTCGHSA enrichment
- 2026-08-23 09:28 UTCVendor advisory
- 2026-08-23 09:28 UTCGHSA enrichment
- 2026-08-23 05:11 UTCVendor advisory
- 2026-08-23 05:11 UTCGHSA enrichment
- 2026-08-23 00:53 UTCEG score recompute
- 2026-08-23 00:53 UTCVendor advisory
- 2026-08-23 00:53 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 20:35 UTCVendor advisory
- 2026-08-22 20:35 UTCGHSA enrichment
- 2026-08-22 16:17 UTCVendor advisory
- 2026-08-22 16:17 UTCGHSA enrichment
- 2026-08-22 11:59 UTCVendor advisory
- 2026-08-22 11:59 UTCGHSA enrichment
- 2026-08-22 07:40 UTCVendor advisory
- 2026-08-22 07:40 UTCGHSA enrichment
- 2026-08-22 03:22 UTCEG score recompute
- 2026-08-22 03:22 UTCVendor advisory
- 2026-08-22 03:22 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 23:04 UTCGHSA enrichment
- 2026-08-21 18:44 UTCGHSA enrichment
- 2026-08-21 14:27 UTCGHSA enrichment
- 2026-08-21 10:09 UTCVendor advisory
- 2026-08-21 10:09 UTCGHSA enrichment
- 2026-08-21 05:52 UTCVendor advisory
- 2026-08-21 05:52 UTCGHSA enrichment
- 2026-08-21 01:34 UTCEG score recompute
- 2026-08-21 01:34 UTCVendor advisory
- 2026-08-21 01:34 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:17 UTCVendor advisory
- 2026-08-20 21:17 UTCGHSA enrichment
- 2026-08-20 16:59 UTCVendor advisory
- 2026-08-20 16:59 UTCGHSA enrichment
- 2026-08-20 12:41 UTCVendor advisory
- 2026-08-20 12:41 UTCGHSA enrichment
- 2026-08-20 08:24 UTCVendor advisory
- 2026-08-20 08:24 UTCGHSA enrichment
- 2026-08-20 04:06 UTCGHSA enrichment
- 2026-08-19 23:49 UTCVendor advisory
- 2026-08-19 23:49 UTCGHSA enrichment
- 2026-08-19 19:31 UTCEG score recompute
- 2026-08-19 19:31 UTCVendor advisory
- 2026-08-19 19:31 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 13:33 UTCVendor advisory
- 2026-08-19 13:33 UTCGHSA enrichment
- 2026-08-19 09:15 UTCVendor advisory
- 2026-08-19 09:15 UTCGHSA enrichment
- 2026-08-19 04:58 UTCVendor advisory
- 2026-08-19 04:57 UTCGHSA enrichment
- 2026-08-19 00:38 UTCVendor advisory
- 2026-08-19 00:38 UTCGHSA enrichment
- 2026-08-18 20:21 UTCVendor advisory
- 2026-08-18 20:21 UTCGHSA enrichment
- 2026-08-18 15:59 UTCEG score recompute
- 2026-08-18 15:59 UTCVendor advisory
- 2026-08-18 15:59 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 09:49 UTCGHSA enrichment
- 2026-08-18 05:31 UTCGHSA enrichment
- 2026-08-18 01:03 UTCVendor advisory
- 2026-08-18 01:03 UTCGHSA enrichment
- 2026-08-17 19:50 UTCVendor advisory
- 2026-08-17 19:50 UTCGHSA enrichment
- 2026-08-17 14:47 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-18015?
When was CVE-2026-18015 disclosed?
Is CVE-2026-18015 actively exploited?
What is the CVSS score of CVE-2026-18015?
How do I remediate CVE-2026-18015?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18015
Is Your Infrastructure Affected by CVE-2026-18015?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.