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

Sandbox escape in Google Chrome Navigation

IdentifiersCVE-2026-4451CWE-20· Improper Input Validation

CVE-2026-4451 is a high-severity insufficient validation of untrusted input vulnerability in the Navigation component of Google Chrome prior to version 146.0.7680.153. According to the provided content, improper validation in Navigation can be triggered via a crafted HTML page and, if the attacker has already compromised the renderer process, may allow a sandbox escape. The issue affects Chrome/Chromium builds before 146.0.7680.153, with patched Chrome Stable releases including 146.0.7680.153 and 146.0.7680.154 depending on platform.

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 to escape Chrome's renderer sandbox after achieving renderer compromise. This would let the attacker move from code execution or control within the restricted renderer context into a less restricted browser or system context, increasing the likelihood of arbitrary code execution, broader system compromise, or follow-on post-exploitation actions beyond the renderer sandbox boundary.

Mitigation

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

Apply the vendor update as the primary mitigation. Until patching is complete, reduce exposure by limiting access to untrusted websites and HTML content, using browser sandboxing and OS hardening features as designed, and minimizing the chance of initial renderer compromise through broader browser hygiene and rapid deployment of all related Chrome security updates. No specific workaround beyond updating is provided in the supplied content.

Remediation

Patch, then assume compromise.

Update Google Chrome/Chromium to a fixed version. The provided content states that Chrome Stable versions 146.0.7680.153 and 146.0.7680.154 for Windows and macOS, and 146.0.7680.153 for Linux, contain the fix. Any Chrome/Chromium version prior to 146.0.7680.153 should be considered vulnerable based on the supplied description.
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.