What is CVE-2026-10883?
Type Confusion in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
The record classifies CVE-2026-10883 under weakness class 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 138 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.6% probability of exploitation in the next 30 days, higher than 48.7% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 8.4/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-10883 being exploited?
Weaponised exploit code for CVE-2026-10883 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 25 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
- Google: Chrome
How to fix CVE-2026-10883
Vendor advisory: 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-10883
1 tracked threat in the Threadlinqs corpus references CVE-2026-10883, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.