CVE-2026-102321: V8 Type Confusion in Google Chrome
- Vendors
- GoogleMicrosoft Corporation
CVE-2026-102321 is a high-severity type confusion vulnerability in the V8 engine in Google Chrome versions before 154.0.8037.92. A remote attacker can trigger the flaw through a crafted HTML page and execute arbitrary code inside the browser sandbox. Chromium-based browsers incorporating the affected V8 code are also affected. The vulnerability does not, by itself, establish a sandbox escape.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits attacker-controlled native code execution within the sandboxed browser process, potentially compromising the confidentiality, integrity, and availability of resources accessible to that process. Access beyond the sandbox would require an additional vulnerability or another means of crossing that security boundary.
Mitigation
If you can’t patch tonight, do this now.
Until updates are deployed, restrict exposure to untrusted web content and limit use of affected browsers where feasible. Retain browser sandboxing and least-privilege controls, and monitor endpoints for suspicious browser behavior. These measures reduce exposure or potential impact but do not correct the flaw; no vulnerability-specific workaround is established.
Remediation
Patch, then assume compromise.
Update Google Chrome to 154.0.8037.92 or later on Windows and Linux, and 154.0.8037.93 or later on macOS, then relaunch the browser. Update Chromium through the applicable vendor or distribution security packages; Debian trixie provides 154.0.8037.92-1~deb13u1, and Chainguard provides 154.0.8037.92-r0. Update Microsoft Edge to the latest vendor-confirmed fixed release. For Prisma Browser, 154.10.5.93 addresses this CVE; 155.16.5.40 or later addresses the complete associated October security update.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
References
Frequently asked questions
- Is CVE-2026-102321 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-102321 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-102321?
- As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-102321.
- Is there a patch for CVE-2026-102321?
- Update Google Chrome to 154.0.8037.92 or later on Windows and Linux, and 154.0.8037.93 or later on macOS, then relaunch the browser. Update Chromium through the applicable vendor or distribution security packages; Debian trixie provides 154.0.8037.92-1~deb13u1, and Chainguard provides 154.0.8037.92-r0.
- What products are affected by CVE-2026-102321?
- Google Chrome and Microsoft Corporation Edge.
- How severe is CVE-2026-102321?
- CVE-2026-102321 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.34% (28th percentile) as of Nov 16, 2026.
Recent activity
25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.