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

Sandbox escape via use-after-free in XR in Google Chrome on Windows

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

CVE-2026-9890 is a use-after-free vulnerability in the XR component of Google Chrome on Windows prior to 148.0.7778.216. According to the provided advisory text, a remote attacker who had already compromised the renderer process could trigger the flaw via a crafted HTML page and potentially escape Chrome's sandbox. The issue is classified by Chromium as Critical. Based on the available information, the bug is a memory-safety error in XR where freed memory may be reused, creating a path from renderer compromise to a higher-impact post-exploitation condition on Windows.

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 could allow an attacker who already achieved code execution or equivalent control within the Chrome renderer process to break out of the renderer sandbox on affected Windows systems. This would significantly increase the attacker's privileges and access relative to a renderer-only compromise, enabling follow-on actions outside normal sandbox restrictions.

Mitigation

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

No specific workaround is provided in the supplied content. The practical mitigation is to apply the vendor patch as soon as possible. Standard risk-reduction measures include limiting exposure to untrusted web content and using current Chrome/Chromium builds with all security updates applied, but no temporary mitigation is documented here for the underlying flaw.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on Windows to version 148.0.7778.216 or later. More generally, deploy the latest Chrome 148.0.7778.216/217 Stable build for Windows as made available by Google's rollout. Debian users of Chromium should apply the vendor-provided fixed package versions where applicable.
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.

ACTIVITY FEED

Recent activity

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

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 activity

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