Advisory

CVE-2026-85046: Google Chromium V8 Type Confusion Enables Remote Code Execution

A type confusion flaw in Google Chrome's V8 JavaScript engine allows a remote attacker to execute arbitrary code inside the browser sandbox simply by luring a user to a malicious web page. The vulnerability carries a CVSS score of 8.8 (HIGH) and has been confirmed as actively exploited, earning a place in the CISA Known Exploited Vulnerabilities catalog.

TL;DR: Update Google Chrome to version 152.0.7977.82 or later—and apply equivalent updates for any Chromium-based browser such as Microsoft Edge or Opera—immediately. CISA's BOD 26-04 mandates timely remediation for federal agencies, and all organizations should treat this as urgent.

What Is the Flaw?

CVE-2026-85046 is a type confusion vulnerability (CWE-843) in V8, the open-source JavaScript and WebAssembly engine at the heart of Google Chrome and every other Chromium-based browser. Type confusion arises when a program allocates or uses a resource as one type but later treats it as a different, incompatible type. In memory-unsafe languages this mismatch can corrupt internal state in ways an attacker controls.

According to the NVD description, the flaw allows a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. In practice this means a victim only needs to visit—or be redirected to—a malicious page for the attack to begin; no file download or additional interaction is required beyond loading the page.

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects:

  • Network-deliverable — reachable over the internet.
  • Low attack complexity — no special conditions or race windows to exploit.
  • No privileges required — the attacker needs no account on the victim system.
  • User interaction required — the victim must visit the crafted page.
  • High confidentiality, integrity, and availability impact — full compromise within scope.

Who and What Is Affected?

Any system running Google Chrome prior to version 152.0.7977.82 is vulnerable. Because V8 is shared across the Chromium open-source project, CISA's KEV entry explicitly notes that the vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

High-risk environments include:

  • End-user workstations where Chrome or another Chromium-based browser is used for everyday browsing.
  • Kiosk or public-facing systems running an unpatched Chromium browser.
  • Developer machines using embedded Chromium runtimes (Electron-based applications, for example).
  • Federal and government systems subject to CISA's Binding Operational Directive 26-04.

Organizations that have not yet inventoried which Chromium-based browsers are installed across their estate should do so as a first step.

Potential Impact

Successful exploitation places attacker-controlled code inside the Chrome renderer sandbox. While a full sandbox escape would require an additional vulnerability, code execution within the sandbox is itself a serious capability that can:

  • Read browser memory, including cached credentials, session tokens, and form data.
  • Serve as a staging point for chaining a second vulnerability to fully escape the sandbox and compromise the host operating system.
  • Silently redirect users to further malicious infrastructure.

CISA has added this vulnerability to the Known Exploited Vulnerabilities catalog (added 2026-09-04), confirming that exploitation has been observed in the wild. The CVSS score of 8.8 HIGH reflects the breadth of potential damage—high impact to confidentiality, integrity, and availability—even before any sandbox-escape component is considered.

The low attack complexity rating means exploitation does not depend on unusual conditions; a broadly distributed malicious advertisement, phishing link, or compromised website is sufficient delivery.

What to Do Now

Take the following steps in priority order:

  1. Patch immediately. Update Google Chrome to 152.0.7977.82 or later. Apply equivalent vendor-issued updates for Microsoft Edge, Opera, and any other Chromium-based browsers in your environment. Consult each vendor's own security advisory for exact version numbers.
  2. Inventory Chromium-based browsers. Include desktop browsers, embedded runtimes (e.g., Electron apps), and browsers on managed mobile devices. Unmanaged or shadow-IT browsers are a common gap.
  3. Prioritize internet-exposed and high-value endpoints. Per CISA's BOD 26-04 guidance referenced in the KEV required action, evaluate each asset's internet exposure when setting remediation timelines.
  4. Apply CISA's BOD 26-04 Forensics Triage Requirements if you are a federal agency or if your organization has adopted equivalent frameworks. CISA's required action states that if mitigations are unavailable, use of the product should be discontinued.
  5. Verify auto-update mechanisms. Chrome typically updates automatically, but managed enterprise deployments sometimes defer or disable auto-update. Confirm that group policy or MDM settings are not blocking the patch.
  6. Monitor for indicators of compromise. Given confirmed in-the-wild exploitation, review browser and endpoint logs for anomalous renderer process behavior, unexpected child processes spawned by browser processes, or unusual outbound connections initiated shortly after browser sessions.

Primary references: CISA KEV Catalog, NVD entry for CVE-2026-85046, and Google's Chrome release channel announcements.

How External Security Testing Surfaces This Exposure

An external attacker scanning your organization sees the same attack surface as a real threat actor: publicly reachable services and, critically, the browser environment that employees use to reach the internet. Point-in-time external vulnerability assessments can help by:

  • Enumerating browser versions visible through authenticated or agent-based scans of managed endpoints, flagging those below the patched threshold.
  • Identifying unmanaged or shadow-IT devices that connect to corporate resources but fall outside routine patch management.
  • Validating patch deployment completeness after the update is pushed, confirming that all targeted hosts actually received the fix rather than relying solely on deployment tool reports.
  • Flagging Chromium-based embedded runtimes (such as Electron applications) that share the vulnerable V8 engine but may not be covered by browser-centric patch policies.

Because exploitation of CVE-2026-85046 requires only a user to visit a crafted page, organizations should also evaluate their email filtering, DNS-layer controls, and web proxy policies as complementary defenses that reduce the likelihood of a user reaching a malicious page in the first place.

Sources & further reading: NVD CVE-2026-85046 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: chromereleases.googleblog.com, issues.chromium.org, github.com, github.com. This advisory contains no exploit code.

Frequently asked questions

Does visiting any website put me at risk, or only suspicious ones?

Any website—including legitimate sites that serve third-party advertisements or have been compromised—could potentially deliver a crafted HTML page exploiting this flaw. The low attack complexity means no special victim action beyond loading a page is needed. Patching to Chrome 152.0.7977.82 or later is the definitive mitigation.

Is Microsoft Edge or Opera also vulnerable?

CISA's KEV entry states the vulnerability could affect multiple browsers that utilize Chromium, explicitly naming Microsoft Edge and Opera among others. Check each vendor's security advisories for the specific patched version numbers applicable to those products.

Does sandbox containment limit the damage?

Chrome's sandbox reduces—but does not eliminate—the risk. The vulnerability achieves code execution inside the sandbox. While a full host compromise would require a separate sandbox-escape vulnerability, in-sandbox code execution is itself a serious capability that can expose sensitive browser data and serve as a stepping stone to further attack.

How do I confirm my Chrome installation is fully patched?

Open Chrome and navigate to <code>chrome://settings/help</code>. The page will display the current version and trigger an update check. The patched version is 152.0.7977.82 or higher. For enterprise deployments, also verify that your MDM or group policy configuration is not deferring updates, and confirm affected hosts via your endpoint management console.