What is CVE-2026-19176?
Use after free in Skia in Google Chrome prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
The record classifies CVE-2026-19176 under weakness class CWE-416. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 83 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 7.5 — HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 0.5% probability of exploitation in the next 30 days, higher than 41.3% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 7.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-08-06, last modified 2026-08-07
Is CVE-2026-19176 being exploited?
Weaponised exploit code for CVE-2026-19176 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 37 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
- Google: Chrome
How to fix CVE-2026-19176
Vendor advisory: https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_01193673229.html. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-19176
1 tracked threat in the Threadlinqs corpus references CVE-2026-19176, either in the campaign’s CVE list or as an indicator on the campaign record.
- Google Chrome 151 Update Fixes 41 Security Vulnerabilities, Including 6 Critical Flaws — CRITICAL · 2026-08-07
Sources
Enriched from CVE.org, NVD, FIRST EPSS, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.