EUVD-2026-40752
GHSA-w6vr-48rr-ggrr
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Renderer-compromise prerequisite elevates AC to H; no system auth required (PR:N); user must visit crafted page (UI:R); integrity-only impact with no confidentiality or availability effect.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in PageInfo in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
Navigation restriction bypass in Google Chrome prior to 150.0.7871.47 enables attackers who have already achieved renderer process compromise to escape certain navigation-level security controls via a crafted HTML page. The flaw resides in the PageInfo component, which handles page metadata, security indicators, and related navigation policy enforcement, and fails to adequately validate attacker-controlled input passed from a compromised renderer. …
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 the Chrome renderer process - this is a hard prerequisite and the primary barrier to exploitation. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N, score 6.5) overstates practical exploitability: AC:L does not account for the significant prerequisite of a compromised renderer, which typically requires exploiting a separate, higher-severity vulnerability before this flaw can be reached. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first delivers a separate, higher-severity exploit - such as a memory corruption flaw in the V8 JavaScript engine or Blink renderer - causing the victim's Chrome renderer process to execute attacker-controlled code when the user visits a malicious page. With the renderer under their control, the attacker then sends crafted input to the PageInfo component in the browser process, exploiting the insufficient validation flaw to bypass navigation restrictions and potentially navigate to origins or resources that would otherwise be blocked by security policy. … |
| Remediation | Update Google Chrome to version 150.0.7871.47 or later - this is the vendor-confirmed fixed release per the Stable Channel advisory at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. … 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 allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today