# CVE-2026-85046: Google Chromium V8 Type Confusion

> A type confusion flaw in V8 allows remote attackers to execute arbitrary code inside the sandbox via a crafted HTML page.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 4 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-85046, ECHO-4025-c648-af1f, GHSA-84qv-4wj5-wwmm, MINI-wjc2-fcfc-q89x

## What is CVE-2026-85046?

CVE-2026-85046 is a high-severity memory corruption vulnerability in Google Chrome, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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)

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2026-85046?

It affects 2 products.


Products: Google Chrome, Google V8.

## How do I fix CVE-2026-85046?

Upgrade to a fixed version. US federal agencies must fix it by 18 Sep 2026.

## Is CVE-2026-85046 being exploited?

Yes. Attackers have exploited CVE-2026-85046 in the wild since at least 4 Sep 2026.

Public exploit code:

- CVE-2026-85046 | Chrome V8 Type Confusion in Inline Array.prototype.sort (Maglev/Turbofan) | CVSS 8.8 | CWE-843 | Chrome < 152.0.7977.82 (github_poc): https://github.com/atiilla/CVE-2026-85046
- https://github.com/adriyansyah-mf/cve-2026-85046-poc (github_poc): https://github.com/adriyansyah-mf/cve-2026-85046-poc
- CVE-2026-85046 (github_poc): https://github.com/HORKimhab/CVE-2026-85046
- https://github.com/SneakyNachos/CVE-2026-85046-who-put-the-silverback-guerilla-in-the-wasm (github_poc): https://github.com/SneakyNachos/CVE-2026-85046-who-put-the-silverback-guerilla-in-the-wasm
- Conceptual C++ patch and structural analysis for CVE-2026-85046, a critical type confusion zero-day vulnerability in Google Chrome's V8 engine (github_poc): https://github.com/ubitquity/CVE-2026-85046-Patch-confusion-zero-day-vulnerability-in-Google-Chrome-s-V8-engine
- https://github.com/Eliot-code/CVE-2026-85046 (github_poc): https://github.com/Eliot-code/CVE-2026-85046

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-11645](https://insights.sbomify.com/CVE-2026-11645/): Google Chromium V8 Out-of-Bounds Read and Write (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85046 and fix it if it is affected.

What it is: CVE-2026-85046 is a high-severity memory corruption vulnerability in Google Chrome, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2026-85046 in the wild since at least 4 Sep 2026.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85046/ (Markdown: https://insights.sbomify.com/CVE-2026-85046/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85046
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85046
- OSV: https://osv.dev/vulnerability/CVE-2026-85046

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85046/
Summaries are generated and may contain mistakes; the official description above is the record.