Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious HTML page
-
DeliveryDeliver page to victim via local means
-
ExploitVictim opens page in unpatched Chrome
-
ExecutionTrigger DevTools policy enforcement gap
-
PersistBypass browser navigation restrictions
-
ImpactRedirect or override navigation controls
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V4 - API and Web Service Server-side security enforcement
|
| Exploitation Conditions | Exploitation requires a victim to open a crafted HTML page in a version of Google Chrome prior to 151.0.7922.72, constituting mandatory user interaction (UI:R per CVSS). The CVE description explicitly identifies a 'local attacker' as the threat actor, suggesting the attack may depend on local delivery of the crafted page rather than remote network delivery - this conflicts with the AV:N CVSS metric and should be verified with the vendor. DevTools must be accessible in the browser, which is the default state for standard Chrome installations (not enterprise-restricted deployments). Exploitation is limited by: required user interaction (victim must actively open the crafted page), the local attacker context stated in the description, the absence of scope change (S:U), and Google's own low-severity classification. The CVSS PR:N metric indicates no attacker authentication or privileges are required to craft the malicious page. |
| Impact | Despite a CVSS 3.1 base score of 6.5 with an integrity-high impact rating, multiple signals collectively indicate low real-world exploitation priority. The EPSS score of 0.12% at the 2nd percentile reflects near-negligible automated exploitation probability. Google's internal Chromium security team rated this 'Low' severity, which is atypical for high-integrity-impact vulnerabilities and suggests constrained practical impact. The attack requires user interaction (UI:R), meaning passive delivery is insufficient - a victim must actively open the crafted HTML page. A notable conflict exists between the CVE description, which specifies 'local attacker', and the provided CVSS AV:N vector; these designations are inconsistent and should be verified against the vendor advisory. If the local attacker characterization is accurate, the real-world attack surface is substantially narrower than AV:N implies. No public exploit code and no CISA KEV listing further reduce urgency. This is a low-real-world-risk finding that warrants patching on a normal update cycle but does not require emergency response. |
| Exploit ScenarioDerived | A local attacker prepares a crafted HTML page that triggers insufficient policy enforcement within Chrome's DevTools component. When the targeted user opens this page in an unpatched version of Chrome (prior to 151.0.7922.72), the attacker's page subverts navigation restrictions, potentially redirecting the browser to attacker-controlled destinations or bypassing navigation-based security controls. No public exploit code has been identified at time of analysis, and the low EPSS score and Google 'Low' severity rating suggest exploitation remains theoretical. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Navigation restriction bypass in Google Chrome's DevTools component (versions prior to 151.0.7922.72) allows a local attacker to circumvent browser navigation policies via a crafted HTML page. The insufficient policy enforcement within DevTools produces an integrity-high impact (CVSS I:H) without requiring attacker privileges. No public exploit code or CISA KEV listing exists; an EPSS score of 0.12% (2nd percentile) and Google's internal 'Low' Chromium severity rating together confirm this as a low immediate exploitation priority.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later, which is confirmed as the vendor-released patch per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome's automatic update mechanism typically handles this without manual intervention; verify the installed version by navigating to chrome://settings/help. As a compensating control prior to patching, enterprise administrators can restrict DevTools access via the DeveloperToolsAvailability enterprise policy (set to 2 to disable DevTools entirely), which eliminates the vulnerable surface; note this trade-off is significant as it breaks all developer workflows and browser debugging capabilities for managed users. No additional workarounds are identified in the available advisory data.
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
The vulnerability resides in the DevTools component of Google Chrome (CPE: cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*), the Chromium-based browser deployed at global scale. Chrome DevTools is an embedded suite of debugging and inspection tools that operates with elevated browser-internal trust. The flaw represents insufficient enforcement of navigation policies within the DevTools context, meaning security controls that restrict or govern page navigation - such as browser-internal navigation guards - are not properly applied when DevTools is involved. No CWE is assigned in the available data, but the behavior is consistent with CWE-358 (Improperly Implemented Security Check for Standard) or CWE-693 (Protection Mechanism Failure). The attack vector involves a crafted HTML page, indicating the policy bypass is triggered through DevTools' interaction with attacker-controlled page content. The Chromium issue tracker entry (https://issues.chromium.org/issues/519232592) is cited as a reference but internal details are not confirmed accessible.
Know when the next one hits your stack
- 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
Sources disagree (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Description explicitly names a local attacker, warranting AV:L over the provided AV:N; user must open crafted HTML (UI:R); only integrity is impacted via navigation bypass.
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
3DescriptionCVE.org
Insufficient policy enforcement in DevTools in Google Chrome prior to 151.0.7922.72 allowed a local attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Low)
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Related Vulnerabilities in Google Chrome Implementation and Policy Flaws
View all 50Same 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 |
EUVD-2026-50900
GHSA-p25h-4wcw-9pr8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB