EUVD-2026-50855
GHSA-h7xm-jv8p-85xm
Severity by source
Sources disagree (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Network-delivered via malicious file requiring active user interaction; integrity-only impact from navigation bypass with no scope change or confidentiality loss.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in DevTools in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to bypass navigation restrictions via a malicious file. (Chromium security severity: Low)
AnalysisAI
Navigation restriction bypass in Google Chrome's DevTools component prior to version 151.0.7922.72 allows a remote attacker to subvert browser navigation controls by delivering a malicious file that triggers insufficient input validation. Exploitation requires user interaction (opening the crafted file), limits opportunistic mass exploitation, and impact is confined to high integrity loss with no confidentiality or availability effects. No active exploitation is confirmed - EPSS stands at 0.17% (7th percentile), and no CISA KEV listing is present - indicating low observed threat activity at time of analysis.
Technical ContextAI
The vulnerability originates in Chrome's DevTools subsystem and is classified as CWE-20 (Improper Input Validation), meaning the component fails to adequately sanitize or reject untrusted input before acting on it. DevTools is a browser-integrated suite for debugging and inspecting web content; its input-handling paths can be reached via crafted files that trigger internal DevTools processing. The affected product scope per CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) covers all desktop platforms running Chrome prior to 151.0.7922.72. The CVSS vector's S:U (unchanged scope) indicates exploitation remains contained within the browser's security context and does not cross into the underlying OS. The navigation restriction bypass as an outcome suggests the flaw allows an attacker to redirect or inject into browsing contexts that would normally be protected by Chrome's navigation policies.
RemediationAI
The primary fix is to update Google Chrome to version 151.0.7922.72 or later, as confirmed by the vendor advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome typically auto-updates on desktop platforms; administrators should verify deployment status via chrome://settings/help or fleet management tooling. For enterprise environments where immediate patching is constrained, a compensating control is to restrict DevTools access using Chrome Enterprise Policy (DevToolsAvailability policy set to 'DeveloperToolsDisabled' or 'DeveloperToolsDisallowed') - note this disables legitimate developer functionality as a trade-off. Additionally, user awareness training to avoid opening files from untrusted sources reduces exposure given the UI:R prerequisite. No upstream workaround short of the policy restriction is documented in available references.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today