CVE-2026-4451: Google Chrome · Insufficient Validation of Untrusted Input
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 146.0.7680.153 soon.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 146.0.7680.153
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade Google Chrome to 146.0.7680.153.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-4451, organizations should immediately update all instances of Google Chrome to version 146.0.7680.153 or later, where the vulnerability has been addressed. Beyond patching, organizations should implement strict web content filtering and block access to known malicious websites to reduce the risk of users encountering crafted HTML pages designed to exploit this flaw. Employing endpoint detection and response (EDR) solutions capable of monitoring unusual behavior in browser renderer processes can help detect attempts to escape the sandbox. User education on the risks of visiting untrusted websites and recognizing phishing attempts is critical to reduce user interaction-based exploitation. Additionally, enforcing the principle of least privilege on user accounts and running browsers with limited permissions can minimize the impact of a successful sandbox escape. Network segmentation and application whitelisting can further contain potential breaches. Regularly reviewing browser security settings and disabling unnecessary plugins or extensions reduces the attack surface. Finally, organizations should monitor threat intelligence feeds for any emerging exploits targeting this vulnerability to respond promptly.
Description
Insufficient validation of untrusted input in Navigation in Google Chrome prior to 146.0.7680.153 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)