Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCompromise renderer process via malicious website
-
DeliveryCraft HTML page with invalid navigation input
-
ExploitBypass sandbox validation checks
-
ExecutionEscape sandbox isolation
-
ImpactExecute arbitrary code with elevated privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Requires Google Chrome versions prior to 146.0.7680.153 with compromised renderer process. Victim must open a crafted HTML page. Attack chains from browser vulnerabilities enabling renderer compromise, then sandbox escape via navigation validation bypass. |
| Impact | Risk assessment is constrained by unavailable CVSS vector and EPSS scores, but multiple factors indicate this is a legitimate high-priority vulnerability. First, the attack vector requires prior renderer compromise, which is a significant prerequisite—this is a post-compromise privilege escalation rather than a direct remote code execution vector. However, renderer compromises are routinely achieved through JavaScript exploits or malicious website visits, making the two-stage attack realistic. Second, the vulnerability is confined to navigation input validation (a well-audited component), reducing likelihood of widespread zero-day exploitation. Third, patch availability and vendor response indicate this was responsibly disclosed and patched. The High severity rating from Chromium reflects the significant impact (sandbox escape = full system compromise) despite moderate accessibility. SSVC framing: exploitation is Functional (patch available), impact is Total (sandbox escape), and automatable exploitation is Moderate (requires prior renderer access). Real-world priority should be elevated due to the post-compromise privilege escalation scenario, but this is not a widespread unpatched zero-day. |
| Exploit ScenarioDerived | An attacker first compromises a victim's Chrome renderer process through a traditional vector such as a malicious website, malware injection, or JavaScript exploit. Once in the renderer sandbox, the attacker crafts a specially designed HTML page (or navigates the compromised renderer to one) containing input that bypasses Navigation component validation. The malformed navigation input is processed by the browser kernel process, allowing the attacker to escape the renderer sandbox and execute arbitrary code with the privileges of the Chrome process (typically the user's full privilege level). This converts a renderer-level compromise into full host system compromise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 20, 2026
A renderer process sandbox escape vulnerability exists in Google Chrome prior to version 146.0.7680.153 due to insufficient input validation in the Navigation component. An attacker who has already compromised the renderer process can exploit this via a crafted HTML page to escape the sandbox and gain elevated privileges on the host system. A patch is available from Google, and the vulnerability is tracked in the EUVD database with High severity classification.
RemediationAI
Upgrade Google Chrome to version 146.0.7680.153 or later immediately. Chrome's auto-update feature will deploy this patch automatically to most users; administrators managing Chrome via policy can force updates using the ChromeVersion policy or enterprise deployment tools. For Debian-based systems, update the chromium or chromium-browser package via apt-get update && apt-get upgrade. No workarounds are available for this vulnerability since it affects core sandbox isolation; patching is the only mitigation. Enterprise users should verify deployment of version 146.0.7680.153 or later across all managed Chrome instances. Consult the vendor advisory at https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_18.html for release notes and https://issues.chromium.org/issues/487768779 for technical context.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability resides in Chrome's Navigation subsystem, which handles URL parsing, page transitions, and cross-origin communication. The root cause is classified as CWE-20 (Improper Input Validation), indicating that untrusted input from a malicious HTML page is not adequately sanitized before being processed by navigation logic. The Navigation component operates at the boundary between the sandboxed renderer process and the browser kernel process; insufficient validation allows an attacker to craft malicious HTML that bypasses security checks meant to enforce process isolation. While CVSS vector details are unavailable, the attack is classified as High severity by Chromium security engineering, suggesting non-trivial complexity but significant impact potential. The vulnerability affects Chrome versions up to and including 146.0.7680.153, with the fix available in the stable channel release dated March 2026.
Know when Chrome gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
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)
Executive ViewAI
Organizations using Navigation in Google Chrome face significant risk from CVE-2026-4451, a input validation vulnerability rated CVSS 8.8. Successful exploitation could significantly impact the confidentiality, integrity, or availability of affected systems. A patch is available and should be applied as part of regular vulnerability management.
Apply vendor patch. If immediate patching is not feasible: (1) Implement network-level access controls to limit exposure; (2) Enable enhanced monitoring and alerting; (3) Apply principle of least privilege.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in Google Chrome 146.0.7680.153 Memory Corruption
View all 26Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
Ubuntu
Priority: Medium| Release | Status | Version |
|---|---|---|
| jammy | not-affected | code not present |
| noble | not-affected | code not present |
| questing | not-affected | code not present |
| upstream | released | - |
Debian
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bullseye (security), bullseye | vulnerable | 120.0.6099.224-1~deb11u1 | - |
| bookworm | fixed | 146.0.7680.153-1~deb12u1 | - |
| bookworm (security) | fixed | 146.0.7680.153-1~deb12u1 | - |
| trixie | fixed | 146.0.7680.153-1~deb13u1 | - |
| trixie (security) | fixed | 146.0.7680.153-1~deb13u1 | - |
| forky | vulnerable | 146.0.7680.80-1 | - |
| sid | fixed | 146.0.7680.153-1 | - |
| bullseye | fixed | (unfixed) | end-of-life |
| (unstable) | fixed | 146.0.7680.153-1 | - |
SUSE
Severity: High| Product | Status |
|---|---|
| SUSE Package Hub 15 SP6 | Fixed |
| openSUSE Leap 15.6 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP6 | Fixed |
EUVD-2026-13468
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB