CVE-2026-17823

chromium-browser: Google Chrome: Same-Origin Policy Bypass via Insufficient Policy Enforcement in WebXR

Published Jul 30, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
Insufficient policy enforcement in WebXR in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Medium)

Analysis

AI-generated

Technical impact

Insufficient policy enforcement in the WebXR subsystem of Google Chrome before version 151.0.7922.72 permits a remote attacker to bypass the browser’s same‑origin policy. By delivering a specially crafted HTML page that triggers a WebXR request, the attacker can read or interact with documents or data that would normally be protected, enabling unauthorized disclosure of confidential information. The weakness is classified as CWE‑346, a failure to restrict a function to its appropriate context.

Affected Systems

Google Chrome browsers older than 151.0.7922.72 on desktop platforms are affected. The vulnerability applies to the standard Chrome product across Windows, macOS, and Linux distributions; no additional vendor or product variants are listed.

Risk and Exploitability

The CVSS score of 6.5 classifies the issue as Medium severity, and the EPSS score of less than 1 % indicates that exploitation is currently unlikely. The vulnerability is not included in the CISA Known Exploited Vulnerabilities catalog. Attack vector is remote and requires the victim to load a malicious web page containing an engineered WebXR request. No user authentication or elevated privileges are needed; the impact is confined to the victim’s browser session, primarily compromising confidentiality of web content.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Google Chrome to version 151.0.7922.72 or later, which implements the WebXR policy fix.
  • If an upgrade is not immediately possible, disable WebXR support by launching Chrome with the flag "--disable-webxr" or by configuring an enterprise policy to block WebXR APIs.
  • Educate users to avoid visiting untrusted or spoofed WebXR‑enabled sites and enforce strict content‑security policies to reduce the likelihood of malicious page delivery.

Generated by OpenCVE AI on August 2, 2026 at 06:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4710-1 chromium security update
Debian DSA Debian DSA DSA-6408-1 chromium security update
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}

Type Values Removed Values Added
Title chromium-browser: Google Chrome: Same-Origin Policy Bypass via Insufficient Policy Enforcement in WebXR
Weaknesses CWE-346
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N'}

threat_severity

Important

Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Description Insufficient policy enforcement in WebXR in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Medium)
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Jul 31, 2026, 3:28 PM
Reserved
Jul 27, 2026, 11:34 PM
Status
Analyzed
Published
Jul 30, 2026, 1:16 AM
Modified
Oct 23, 2026, 11:10 PM
Severity
Important
Public date
Jul 30, 2026, 12:19 AM