CVE-2026-85046
KEVGoogle Chromium V8 Type Confusion Vulnerability
Description
Google Chromium V8 contains a type confusion vulnerability that allows a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
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)
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HPublishedSep 3, 2026
Last modifiedSep 21, 2026
Added to KEVSep 4, 2026
Remediation dueSep 18, 2026
References
- chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01882797386.htmlRelease NotesVendor Advisory
- issues.chromium.org/issues/542403045Permissions Required
- github.com/Serotav/Writeups/blob/77556c57999805fa7815a114da51d91cf24fbea9/v8/When_Sorting_Leads_To_Confusion.mdExploitThird Party Advisory
- github.com/v8/v8/commit/e0562d87ad9c17042b581582c99237d798572e67Patch
- news.ycombinator.com/item?id=49570669Issue TrackingThird Party Advisory
- serotav.github.io/Writeups/v8/when-sorting-leads-to-confusion/ExploitThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-85046US Government Resource
0 recent articles mention this CVE
74
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 39 days
- CVSS
- 8.8 HIGH
- EPSS (30-day exploit probability)
- 1.8% · top 22% of all CVEs
- Weakness
- CWE-843
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.