CVE-2026-85046
Google Chromium V8 Type Confusion Vulnerability
Description
CVE-2026-85046 is a high-severity type confusion vulnerability in the V8 JavaScript engine of Google Chrome that allowed a remote attacker to execute arbitrary code inside the browser sandbox via a crafted HTML page. Google Chrome prior to version 152.0.7977.82 and V8 before 15.3.48 are affected, and Chromium rates the internal security severity as High. A victim only needs to load an attacker-controlled or compromised page for this V8 vulnerability to trigger, making it a practical drive-by attack vector. CVE-2026-85046 carries a CVSS score of 8.8, has public exploit write-ups available, and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog with a remediation deadline of 18 September 2026.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| chrome | < 152.0.7977.82 | |
| v8 | < 15.3.48 |
References
- https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01882797386.html(Release Notes, Vendor Advisory)
- https://issues.chromium.org/issues/542403045(Permissions Required)
- https://github.com/Serotav/Writeups/blob/77556c57999805fa7815a114da51d91cf24fbea9/v8/When_Sorting_Leads_To_Confusion.md(Exploit, Third Party Advisory)
- https://github.com/v8/v8/commit/e0562d87ad9c17042b581582c99237d798572e67(Patch)
- https://news.ycombinator.com/item?id=49570669(Issue Tracking, Third Party Advisory)
- https://serotav.github.io/Writeups/v8/when-sorting-leads-to-confusion/(Exploit, Third Party Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-85046(US Government Resource)
Weakness Type
CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')
Type confusion occurs when a product allocates or initialises a resource using one type but later accesses it as an incompatible type, so the code operates on memory that lacks the properties it assumes — interpreting an integer as a pointer, for example, or reading past a shorter object's real extent. In CVE-2026-85046 V8's optimising execution makes a type assumption that attacker-controlled JavaScript can invalidate, and the resulting mismatched access gives the attacker a memory corruption primitive inside the engine.
Learn more: CWE-843 — Access of Resource Using Incompatible Type ('Type Confusion')
Impact Analysis
CVE-2026-85046 is remotely exploitable over the network with low attack complexity and no privileges required, but it does require user interaction — the victim has to load a crafted HTML page, which in practice means visiting a malicious site, opening a compromised legitimate page, or rendering an attacker-controlled advertisement or iframe. Once triggered, the impact is high for confidentiality, integrity and availability within the affected component: arbitrary code execution in the renderer process exposes the data that process handles, including page content and session material, and lets the attacker manipulate or crash it. The scope is UNCHANGED, reflecting that execution remains confined to the Chrome sandbox — full host compromise would require chaining a separate sandbox escape, which is a routine second stage in real exploit chains. With a CVSS 3.1 base score of 8.8 (High), an EPSS score of roughly 1.3% (68th percentile), published exploit write-ups and CISA KEV listing, this is a browser update that should not wait for a maintenance window.
Exploit Maturity
CISA has confirmed active exploitation of CVE-2026-85046 by adding it to the Known Exploited Vulnerabilities catalog with an 18 September 2026 remediation deadline. Public exploit write-ups are available: a detailed technical analysis titled "When Sorting Leads To Confusion" is published both on GitHub and as a hosted write-up, and the upstream V8 fix commit is public, which lets anyone diff the patch to locate the vulnerable logic precisely. That combination — confirmed in-the-wild use, a published analysis and a visible patch — puts this vulnerability at the high end of exploit maturity for a browser bug. The EPSS score of about 1.3% (68th percentile) lags the actual situation, as EPSS handles client-side, user-interaction-driven vulnerabilities poorly. Any Chrome installation still below 152.0.7977.82 should be regarded as exposed to drive-by attack.
Remediation
- Follow the CISA KEV required action. Apply mitigations in accordance with Google's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date is 18 September 2026.
- Update Google Chrome to 152.0.7977.82 or later. All earlier versions are affected, as is V8 before 15.3.48; the fix shipped in the Chrome Stable desktop channel, and Chrome applies it only after a relaunch, so verify via chrome://settings/help that browsers have actually restarted.
- Enforce the update centrally instead of relying on users. Use Chrome Browser Cloud Management, group policy or your endpoint management platform to mandate the minimum version and trigger a relaunch, and report on rollout coverage rather than assuming auto-update completed across the estate.
- Update all other Chromium-based software. The defect is in V8, so Microsoft Edge, Brave, Opera, Electron applications and any embedded Chromium runtime inherit it until their vendors ship a build containing the patched engine — inventory these and update them alongside Chrome, since Electron apps in particular lag badly.
- Reduce browser exposure and harden long term by keeping site isolation and the sandbox enabled, limiting extensions to a vetted allowlist, deploying ad and script filtering to cut malvertising delivery paths, and treating browser patches as an expedited class of update — V8 type confusion bugs are found regularly and, as this case shows, are analysed publicly within days.
Technical Details
CVE-2026-85046 is a type confusion flaw (CWE-843) in V8, the JavaScript and WebAssembly engine inside Chrome. V8's optimising compiler specialises code around assumptions about object shapes and types; when attacker-controlled JavaScript can invalidate such an assumption without the corresponding guard firing, the optimised code continues to access the object as though it still had the original type. Accessing a resource through an incompatible type means the engine treats fields at the wrong offsets and sizes — an integer may be dereferenced as a pointer, or a read may run past a shorter object's real bounds — giving the attacker the arbitrary read and write primitives that lead to code execution inside the renderer. The published research titled "When Sorting Leads To Confusion" indicates the confusion arises through array sorting behaviour, a classic route for invalidating type assumptions mid-operation. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H records a network-delivered, low-complexity attack with no privileges but required user interaction and unchanged scope, because execution stays inside the sandbox.
Frequently Asked Questions
Is CVE-2026-85046 being actively exploited?
Yes. CISA added CVE-2026-85046 to its Known Exploited Vulnerabilities catalog with a remediation due date of 18 September 2026, confirming exploitation in the wild. Detailed public exploit write-ups and the upstream V8 fix commit are both available, so the technical barrier to building a working exploit is low.
What products are affected by CVE-2026-85046?
Google Chrome before 152.0.7977.82 and the V8 engine before 15.3.48 are affected. Because V8 is shared, other Chromium-based browsers and embedded runtimes — Microsoft Edge, Brave, Opera and Electron applications — are affected until they ship a build with the fixed engine.
How do I fix CVE-2026-85046?
Update Google Chrome to 152.0.7977.82 or later and relaunch the browser so the patch takes effect. Enforce the minimum version via managed browser policy rather than user-initiated updates, and update every other Chromium-based browser and Electron application in your environment to a build containing V8 15.3.48 or later.
How severe is CVE-2026-85046?
CVE-2026-85046 is rated High with a CVSS 3.1 base score of 8.8, and Chromium's own internal severity rating is also High. It is network-delivered with low complexity and no privileges but requires the victim to open a crafted page, and the code execution stays inside the Chrome sandbox; with confirmed KEV-listed exploitation and public exploit write-ups, updating immediately is warranted.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.