Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Inappropriate implementation in V8 in Google Chrome

IdentifiersCVE-2026-4447CWE-670

CVE-2026-4447 is a high-severity vulnerability in the V8 JavaScript engine in Google Chrome prior to 146.0.7680.153. The provided content describes it as an "inappropriate implementation" issue in V8 that could allow a remote attacker to execute arbitrary code inside the Chrome sandbox by convincing a user to load a crafted HTML page. Supporting context further characterizes the bug as involving a Smi-to-HeapObject confusion path relevant to fake object construction, where exploitation would depend on bypassing HeapObject tag checks.

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 may allow a remote attacker to achieve arbitrary code execution within the Chrome renderer sandbox. Based on the provided content, this is a sandboxed code-execution outcome rather than a full browser or OS compromise by itself.

Mitigation

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

Apply the vendor patch as the primary mitigation. Until patching is complete, reduce exposure by limiting use of untrusted web content, restricting browser execution in high-risk environments, and using Chrome's existing sandboxing and enterprise browser-hardening controls. No specific configuration-based workaround is provided in the content.

Remediation

Patch, then assume compromise.

Update Google Chrome/Chromium to version 146.0.7680.153 or later. The content indicates that Google fixed this issue in Chrome 146.0.7680.153/154, and Chromium-based distributions should apply the corresponding patched release.
PUBLIC EXPLOITS

Exploits

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

VALID 0 / 2 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 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 activity5

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