# CVE-2026-19167 — Google Chrome

> As of 2026-08-07, CVE-2026-19167 is a LOW-severity vulnerability in Google Chrome, CVSS v3.1 3.1, EPSS 0.2% (12.7th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-19167, most recently “Google Chrome 151 Update Fixes 41 Security Vulnerabilities, Including 6 Critical Flaws”.

**Last updated:** 2026-08-07

## What is CVE-2026-19167?

Integer overflow in GPU in Google Chrome prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

The record classifies CVE-2026-19167 under weakness class [CWE-190](https://intel.threadlinqs.com/cwe/CWE-190). 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. 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:** 3.1 — LOW (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 12.7% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.1/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-19167 being exploited?

Weaponised exploit code for CVE-2026-19167 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

- [trickest/cve](https://github.com/trickest/cve/blob/main/2026/CVE-2026-19167.md) (trickest)

## Affected products and versions

- [Google](https://intel.threadlinqs.com/vendors/google): Chrome

## How to fix CVE-2026-19167

No vendor patch reference has been recorded for CVE-2026-19167 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-19167

1 tracked threat in the Threadlinqs corpus references CVE-2026-19167, 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](https://intel.threadlinqs.com/threat/TL-2026-1931) — CRITICAL · 2026-08-07

## Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on 2026-10-10.

**Other references**

- [chromereleases.googleblog.com](https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_01193673229.html)
- [issues.chromium.org](https://issues.chromium.org/issues/536666274)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-19167
Full detection coverage and IOCs for threats exploiting CVE-2026-19167 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp