# CVE-2026-15771 — Google Chrome

> As of 2026-07-14, CVE-2026-15771 is a MEDIUM-severity vulnerability in Google Chrome, CVSS v3.1 5.3, EPSS 0.3% (27.2th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-15771, most recently “Chrome 150 Security Update Fixes 15 Vulnerabilities Including Two Critical Use-After-Free Flaws in Ozone (CVE-2026-15764, CVE-2026-15765)”.

**Last updated:** 2026-07-14

## What is CVE-2026-15771?

Insufficient validation of untrusted input in Media in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: High)

The record classifies CVE-2026-15771 under weakness class [CWE-20](https://intel.threadlinqs.com/cwe/CWE-20). 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. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 106 days ago.

## Severity and exploitation probability

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

## Is CVE-2026-15771 being exploited?

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

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

## Affected products and versions

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

## How to fix CVE-2026-15771

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

1 tracked threat in the Threadlinqs corpus references CVE-2026-15771, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Chrome 150 Security Update Fixes 15 Vulnerabilities Including Two Critical Use-After-Free Flaws in Ozone (CVE-2026-15764, CVE-2026-15765)](https://intel.threadlinqs.com/threat/TL-2026-1368) — CRITICAL · 2026-07-15

## Sources

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

**Other references**

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

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