Skip to main content
Mallory
High

Type Confusion in Bindings in Google Chrome

IdentifiersCVE-2026-11662CWE-843· Access of Resource Using…

CVE-2026-11662 is a high-severity type confusion vulnerability in the Bindings component of Google Chrome affecting versions prior to 149.0.7827.103. According to the provided sources, a remote attacker can trigger the flaw by getting a target to open a crafted HTML page. Successful exploitation allows arbitrary code execution inside the Chrome sandbox. The available content identifies the bug class as type confusion but does not provide function-level or root-cause implementation details beyond its location in Bindings.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to execute arbitrary code within the Chrome sandbox in the context of the browser process handling the malicious content. The supplied CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates potential high impact to confidentiality, integrity, and availability, although the provided material does not state sandbox escape or full system compromise by this CVE alone.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround or temporary mitigation is provided in the supplied content. Practical mitigation is to deploy the patched Chrome/Chromium version as soon as possible. Until patching is complete, reducing exposure to untrusted web content may lower risk, but this is not a vendor-stated mitigation in the provided material.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 149.0.7827.103 or later. Where Chromium is consumed through downstream distributions, apply the vendor-provided fixed packages; the provided Debian advisory references chromium 149.0.7827.102-1~deb12u1 for Debian 12/bookworm and 149.0.7827.102-1~deb13u1 for Debian 13/trixie as the patched builds for the broader vulnerability set.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.