Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Network-reachable via crafted page (AV:N, AC:L, PR:N), mandatory user visit (UI:R), navigation bypass yields low integrity impact only (I:L, C:N, A:N, S:U).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in WebXR in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
Navigation restriction bypass in Google Chrome's WebXR component affects all versions prior to 150.0.7871.47, exploitable by a remote unauthenticated attacker who can induce a user to visit a crafted HTML page. The root cause is insufficient input validation (CWE-20) within the WebXR subsystem, resulting in limited integrity impact via unauthorized navigation. No public exploit exists and EPSS sits at 0.18% (8th percentile), consistent with the Chromium team's own Low severity classification - this represents a genuine but low-priority risk.
Technical ContextAI
WebXR is the browser API enabling immersive VR and AR experiences, exposing hardware device inputs and scene-graph navigation to web content. The vulnerable component failed to apply sufficient validation to untrusted input presented through this API pathway, classified under CWE-20 (Improper Input Validation). The affected CPE scope is Google Chrome on desktop prior to version 150.0.7871.47 across all supported platforms. Because WebXR is a relatively niche browser API surface, exploitation requires a page that specifically exercises WebXR input handling in a way that triggers the validation gap.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later, which is confirmed as the patched release per the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Chrome's auto-update mechanism will deliver this update automatically on most managed and consumer installations - administrators should verify fleet update compliance via Chrome Browser Cloud Management or equivalent MDM tooling. If immediate patching is not feasible, a targeted workaround is to disable or restrict WebXR access via enterprise policy (Chrome's WebXR-related policies such as blocking camera/motion sensor permissions reduce the attack surface); note that this will break any legitimate WebXR applications in the environment. No other compensating controls directly address the underlying input validation flaw.
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
EUVD-2026-40760
GHSA-5x5m-vp5v-xf5w