CVE-2026-85046 — Google Chrome
CISA KEVAs of 2026-09-06, CVE-2026-85046 is a HIGH-severity vulnerability in Google Chrome, CVSS v3.1 8.8, EPSS 1.1% (65.1th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-09-04), with a US federal remediation deadline of 2026-09-18. Threadlinqs Intelligence links 2 tracked threat campaigns to CVE-2026-85046, most recently “Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046)”.
Last updated: 2026-09-06
What is CVE-2026-85046?
Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
The record classifies CVE-2026-85046 under weakness class CWE-843. 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 10 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)
- 1.1% probability of exploitation in the next 30 days, higher than 65.1% of all scored CVEs
- CISA KEV
- Listed since 2026-09-04, federal remediation deadline 2026-09-18
- Threadlinqs priority
- 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
- Published
- 2026-09-03, last modified 2026-09-06
Is CVE-2026-85046 being exploited?
CISA added CVE-2026-85046 to the Known Exploited Vulnerabilities catalog on 2026-09-04, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-09-18 under BOD 22-01. Weaponised exploit code for CVE-2026-85046 is publicly available. 3 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 63 in the Threadlinqs vulnerability feed.
- HORKimhab/CVE-2026-85046 (github)
- adriyansyah-mf/cve-2026-85046-poc (github)
- ubitquity/CVE-2026-85046-Patch-confusion-zero-day-vulnerability-in-Google-Chrome-s-V8-engine (github)
Affected products and versions
- Google: Chrome
How to fix CVE-2026-85046
Vendor advisory: https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01882797386.html. Because CVE-2026-85046 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-09-18. 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-85046
2 tracked threats in the Threadlinqs corpus reference CVE-2026-85046, either in the campaign’s CVE list or as an indicator on the campaign record.
- Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046) — CRITICAL · 2026-09-08
- Google Patches Chrome Zero-Day CVE-2026-85046 (6th of 2026), Actively Exploited V8 Type Confusion — HIGH · 2026-09-04
Sources
Enriched from CVE.org, NVD, FIRST EPSS, CISA KEV, 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.
Other references
← all vulnerabilities · Markdown version · Threadlinqs Intelligence