# CVE-2026-10882 — Google Chrome

> As of 2026-06-05, CVE-2026-10882 is a HIGH-severity vulnerability in Google Chrome, CVSS v3.1 8.8, EPSS 0.4% (38.0th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-10882, most recently “Google AI Agents (Big Sleep, CodeMender, Gemini) Fix 1,072 Chrome Security Bugs Across Chrome 149/150, Including 13-Year-Old ANGLE Sandbox-Escape (CVE-2026-10881)”.

**Last updated:** 2026-06-05

## What is CVE-2026-10882?

Use after free in Network in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

The record classifies CVE-2026-10882 under weakness class [CWE-416](https://intel.threadlinqs.com/cwe/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 123 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.4% probability of exploitation in the next 30 days, higher than 38.0% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 5.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-06-04, last modified 2026-06-05

## Is CVE-2026-10882 being exploited?

No public exploitation evidence for CVE-2026-10882 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-06-05. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.

## Affected products and versions

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

## How to fix CVE-2026-10882

Vendor advisory: [https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.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-10882

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

- [Google AI Agents (Big Sleep, CodeMender, Gemini) Fix 1,072 Chrome Security Bugs Across Chrome 149/150, Including 13-Year-Old ANGLE Sandbox-Escape (CVE-2026-10881)](https://intel.threadlinqs.com/threat/TL-2026-1795) — INFO · 2026-07-31

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-08-01. 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/06/stable-channel-update-for-desktop.html)
- [issues.chromium.org](https://issues.chromium.org/issues/503420443)

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