What is the CVSS score of EUVD-2026-40819?

EUVD-2026-40819 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for EUVD-2026-40819?

Yes, a patch is available for EUVD-2026-40819. Update the affected software to the latest version immediately.

Google Chrome EUVD-2026-40819

| CVE-2026-14132 MEDIUM

User Interface (UI) Misrepresentation of Critical Information (CWE-451)

2026-06-30 chrome-cve-admin@google.com

GHSA-rjp5-8cgw-rxgg

Information Disclosure Google Red Hat Suse

5.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

vuln.today AI

5.4 MEDIUM

Network-delivered via crafted page (AV:N), requires victim navigation (UI:R), no privileges needed (PR:N), impact limited to UI spoofing with no availability effect (C:L/I:L/A:N).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

SUSE

MEDIUM

qualitative

Red Hat

4.3 LOW

qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 18:27 vuln.today

CVSS changed

Jul 01, 2026 - 16:07 NVD

5.4 (MEDIUM)

CVE Published

Jun 30, 2026 - 23:17 nvd

MEDIUM 5.4

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

DescriptionNVD

Inappropriate implementation in WebXR in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)

AnalysisAI

UI spoofing in Google Chrome's WebXR component (all versions prior to 150.0.7871.47) allows remote attackers to misrepresent browser interface elements when a victim visits a crafted HTML page. The flaw stems from an inappropriate implementation in the WebXR Device API, enabling manipulation of what the user perceives as trusted UI - potentially obscuring origin indicators, security state, or page identity. No public exploit code exists and EPSS stands at 0.18% (8th percentile); CISA SSVC rates exploitation as none with partial technical impact, placing this firmly in the lower-priority tier despite its network-accessible vector.

Technical ContextAI

The WebXR Device API (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) enables immersive virtual and augmented reality experiences directly within the browser context. CWE-451 (User Interface Misrepresentation of Critical Information) identifies the root cause: Chrome's WebXR implementation fails to correctly enforce the boundary between application-controlled and browser-controlled UI, allowing a crafted HTML page to influence elements the user would otherwise trust as browser-owned - such as origin indicators, permission prompts, or security chrome. This class of vulnerability is particularly dangerous in immersive contexts where the browser's trusted UI surface is already reduced or obscured by the XR environment. The Chromium tracking issue (514039492) contains additional technical detail that may be access-restricted.

RemediationAI

Upgrade Google Chrome to version 150.0.7871.47 or later via the Chrome stable channel update documented at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html; this is the vendor-confirmed fix and the primary remediation. For enterprise environments unable to patch immediately, WebXR can be disabled via Chrome enterprise policy (WebXrEnabled=false via GPO or chrome://flags/#webxr-incubations), which eliminates the attack surface entirely but also disables all WebXR functionality for end users - a trade-off appropriate only for environments where XR content is not operationally required. Blocking navigation to untrusted external HTML pages via proxy or content filtering provides additional depth but is not a substitute for patching given the low complexity of hosting a malicious page.