EUVD-2026-44485
GHSA-gc92-vpv6-2c4w
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
AC:H reflects the mandatory renderer-compromise prerequisite; all other metrics follow the official vector since network delivery and user interaction are confirmed.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in Navigation in Google Chrome prior to 150.0.7871.125 allowed a remote attacker who had compromised the renderer process to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Navigation input validation bypass in Google Chrome prior to 150.0.7871.125 enables a remote attacker who has already compromised the renderer process to circumvent navigation restrictions through a crafted HTML page. The flaw is classified as a second-stage, chained exploit - the attacker must first achieve renderer process compromise before this vulnerability becomes exploitable. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the attacker has ALREADY achieved code execution within Chrome's renderer process through a separate, prior vulnerability - this is a mandatory prerequisite stated explicitly in the CVE description. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The official CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) warrants scrutiny: the AC:L and PR:N metrics conflict with the description's explicit prerequisite of a compromised renderer process, which is a non-trivial attack condition. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer-level vulnerability to achieve code execution within Chrome's sandboxed renderer process - for example, a JavaScript engine memory corruption bug. Once inside the renderer, the attacker delivers a crafted HTML page that supplies malformed navigation parameters to the Navigation subsystem, bypassing policy restrictions such as frame navigation blocks or CSP directives, and redirecting a privileged browser context to an attacker-controlled destination. … |
| Remediation | Update Google Chrome to version 150.0.7871.125 or later via the browser's built-in update mechanism (Help > About Google Chrome) or enterprise deployment tools (Google Update / SCCM). … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today