Skip to main content
Mallory
HighVulnerability

CVE-2026-102321: V8 Type Confusion in Google Chrome

Published Sep 29, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS8.8High · v3.1
EPSS0.34%28th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
GoogleMicrosoft Corporation
IdentifiersCVE-2026-102321CWE-843 · Access of Resource Using…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
Microsoft CorporationEdgeapplication
FAQ

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.
Activity feed

Recent activity

25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
zdnetNews · Nov 16, 2026L'IA détecte désormais des failles " zero-day " pour seulement 4 ...A type-confusion vulnerability in Google's V8 engine that can lead to remote code execution. According to the article, it was confidentially reported to Google's vulnerability rewards program and used to benchmark seven AI models. Three models detected it; GPT 6 Sol identified it in 13 minutes for $4.24. The research concerns vulnerability discovery, not demonstrated exploitation.Read more ↗zdnet zero dayNews · Nov 16, 2026AI finds zero-day flaws for just $4 now - even mediocre hackers can cash in - ZDNETA type confusion vulnerability in Google's V8 engine that can lead to remote code execution. Researchers used the privately reported flaw to evaluate seven AI models under a restricted source-code review scope. Three models discovered it, with GPT 6 Sol finding it in 13 minutes for $4.24, illustrating the declining cost of AI-assisted vulnerability discovery.Read more ↗tenable cloud security pluginsNews · Oct 7, 2026Chainguard: multiple chromium packages: security update to 154... | Tenable®A high-severity V8 type-confusion vulnerability affecting Google Chrome before version 154.0.8037.92 and corresponding Chainguard Chromium packages. A crafted HTML page can trigger arbitrary code execution inside the browser sandbox; the content does not describe a sandbox escape. The reported CVSS v3 base score is 8.8. The recommended fix is to update Chromium and related packages to version 154.0.8037.92-r0 or later.Read more ↗tenable nessus pluginsNews · Oct 4, 2026Fedora 45 : chromium (2026-0daef29dc3) | Tenable®A Chromium vulnerability referenced by the Fedora security check; vulnerability-specific technical details are not provided.Read more ↗
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.