# CVE-2026-16807 — Google Chrome

> As of 2026-07-24, CVE-2026-16807 is a HIGH-severity vulnerability in Google Chrome, CVSS v3.1 8.8, EPSS 0.2% (16.1th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-16807 as of 2026-07-24; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-24

## What is CVE-2026-16807?

Out of bounds write in Codecs in Google Chrome prior to 150.0.7871.186 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

The record classifies CVE-2026-16807 under weakness class [CWE-787](https://intel.threadlinqs.com/cwe/CWE-787). 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 74 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.8 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 16.1% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-23, last modified 2026-07-24

## Is CVE-2026-16807 being exploited?

It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

## Affected products and versions

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

## How to fix CVE-2026-16807

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

No threat campaign in the Threadlinqs corpus currently references CVE-2026-16807, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on 2026-07-25. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [chromereleases.googleblog.com](https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_01320465736.html)
- [issues.chromium.org](https://issues.chromium.org/issues/518237034)

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