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

Use-after-free in Google Chrome Video

IdentifiersCVE-2026-6302CWE-416· Use After Free

CVE-2026-6302 is a high-severity use-after-free vulnerability in the Video component of Google Chrome. It affects Chrome versions prior to 147.0.7727.101 and can be triggered by a remote attacker through a crafted HTML page. The available supporting content indicates the flaw is a memory-lifetime error in which an object used by the Video component is freed prematurely and later dereferenced. The described exploitation pattern involves a malicious page causing the vulnerable code path to free an object, followed by heap shaping with JavaScript-controlled allocations so the freed memory is reclaimed with attacker-controlled data before the dangling pointer is used. Successful exploitation results in arbitrary code execution within the Chrome renderer sandbox.

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 can allow a remote attacker to execute arbitrary code inside the Chrome browser sandbox in the context of the renderer process. The provided CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates high potential impact to confidentiality, integrity, and availability within that security boundary. The content does not state that this vulnerability alone provides a sandbox escape or full system compromise.

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 access to untrusted web content, blocking or filtering phishing and malvertising delivery paths, and using browser isolation or application sandboxing controls where available. Because exploitation requires visiting attacker-controlled HTML content, restricting user access to untrusted sites and embedded third-party content can reduce risk, but these measures are not substitutes for updating.

Remediation

Patch, then assume compromise.

Update Google Chrome to a fixed version. The supporting content states that all versions prior to 147.0.7727.101 are affected. Google lists secure versions as 147.0.7727.101 or 147.0.7727.102 for Windows and macOS, and 147.0.7727.101 for Linux. Chromium-based browsers that reuse the affected codebase should also be updated once vendor fixes are available.
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 activity3

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