What is CVE-2026-19158?
Use after free in Views in Google Chrome on Windows prior to 151.0.7922.109 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)
The record classifies CVE-2026-19158 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.3% probability of exploitation in the next 30 days, higher than 21.2% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 6.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-08-06, last modified 2026-08-08
Is CVE-2026-19158 being exploited?
Weaponised exploit code for CVE-2026-19158 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 32 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
- Google: Chrome
How to fix CVE-2026-19158
No vendor patch reference has been recorded for CVE-2026-19158 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-19158
1 tracked threat in the Threadlinqs corpus references CVE-2026-19158, 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, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on .