Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Arbitrary Code Execution in Chrome V8 via Crafted HTML Page

IdentifiersCVE-2026-3910CWE-670

CVE-2026-3910 is a high-severity inappropriate implementation vulnerability in the V8 JavaScript/WebAssembly engine in Google Chrome. According to the provided content, affected versions are Chrome prior to 146.0.7680.75/.76, and successful exploitation allows a remote attacker to execute arbitrary code inside the browser sandbox by inducing the target to load a crafted HTML page. Public reporting in the supplied material consistently describes the issue only at a high level as an implementation flaw in V8; no authoritative vulnerable function, root-cause commit, or precise memory-corruption primitive is provided in the source material. One mention in the supplied context claims the issue involved write-barrier elision leading to use-after-free, but that detail is not corroborated by an official advisory in the provided content, so the exact low-level bug mechanism remains currently not available from the supplied sources.

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 enables arbitrary code execution within the Chrome renderer/browser sandbox context. As reflected in the provided reporting, this can give an attacker control over execution inside the sandboxed process and may support follow-on exploitation such as data access within the compromised browser context, staging of additional payloads, or chaining with a sandbox escape or privilege-escalation vulnerability for broader system compromise. The content also states that exploits for this vulnerability existed in the wild and that CISA added it to the KEV catalog, indicating real-world operational significance.

Mitigation

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

Primary mitigation is prompt patching. Where immediate patching is not possible, reduce exposure by limiting access to untrusted web content, restricting JavaScript/WebAssembly execution where operationally feasible, using browser isolation or application control for high-risk users, and monitoring for suspicious browser child processes, anomalous renderer crashes, or unusual outbound connections associated with browser activity. These are compensating controls only; the provided content does not describe a vendor-supplied workaround that fully mitigates the flaw short of updating.

Remediation

Patch, then assume compromise.

Update Google Chrome to a fixed version. The provided content states Google released patches in Chrome 146.0.7680.75 for Windows and Linux and 146.0.7680.76 for macOS, with reporting also referring generally to 146.0.7680.75/.76 as the fixed builds. Organizations should ensure Chrome is updated to at least those versions or later, restart the browser to complete installation, and apply corresponding vendor updates for Chromium-based browsers such as Edge, Brave, Opera, and Vivaldi when available.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

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 signatures2

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 activity55

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