What is the CVSS score of CVE-2026-13864?

CVE-2026-13864 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Google Chrome are affected by CVE-2026-13864?

Google Chrome versions prior to 150.0.7871.47 contain a privilege escalation vulnerability in the WebHID subsystem that allows malicious browser extensions to escape sandbox restrictions and gain…. A patch is available.

How to fix or mitigate CVE-2026-13864?

Within 24 hours: Inventory Chrome versions across the organization and confirm deployment status relative to 150.0.7871.47. Within 7 days: Deploy Google Chrome 150.0.7871.47 or later organization-wide; simultaneously distribute guidance warning against untrusted extension installation. Within 30 days: Verify 100% deployment completion and audit enterprise extension policies to restrict installation from unapproved sources.

Google Chrome CVE-2026-13864

EUVD-2026-40550 HIGH

Improper Access Control (CWE-284)

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

GHSA-hwcm-f47f-gx33

Authentication Bypass Privilege Escalation Google Red Hat Suse

8.1

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

8.1 HIGH

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

vuln.today AI

7.5 HIGH

Requires the victim to install a malicious extension, so UI:R (not UI:N) and AC:H; attacker needs no prior browser privileges (PR:N), and a successful escape yields full C/I/A impact within the browser.

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

4.0 AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

HIGH

qualitative

Red Hat

5.4 MEDIUM

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 15:27 vuln.today

CVSS changed

Jul 01, 2026 - 15:22 NVD

8.1 (HIGH)

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:17 cve.org

HIGH 8.1

DescriptionCVE.org

Insufficient policy enforcement in WebHID in Google Chrome prior to 150.0.7871.47 allowed an attacker who convinced a user to install a malicious extension to perform privilege escalation via a crafted Chrome Extension. (Chromium security severity: Medium)

AnalysisAI

Privilege escalation in Google Chrome desktop prior to 150.0.7871.47 stems from insufficient policy enforcement in the WebHID subsystem, letting a maliciously crafted extension escape its intended boundaries and gain elevated access to human-interface devices and browser privileges. Exploitation first requires convincing a victim to install the malicious extension, after which a crafted Chrome Extension bypasses WebHID access controls. Chromium rates the issue Medium; no public exploit is identified at time of analysis and EPSS exploitation probability is low (0.13%, 3rd percentile).

Technical ContextAI

WebHID is a browser API granting web content and extensions access to Human Interface Devices - keyboards, gamepads, FIDO/U2F security keys, and custom USB peripherals - after a permission grant. The flaw is CWE-284 (Improper Access Control): Chrome's WebHID policy enforcement did not sufficiently restrict what a Chrome Extension could reach, allowing a crafted extension to exceed its intended device-access boundaries and escalate privilege within the browser. Because WebHID bridges web-facing code to physical hardware, weak policy checks here can expose sensitive devices or serve as a stepping stone in a broader extension-based compromise.

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on all desktop platforms; most installations update automatically, so relaunch the browser to apply the update and confirm via chrome://settings/help. In managed environments, push the update through enterprise update tooling. As a compensating control until patched, restrict extension installation via enterprise policy (set ExtensionInstallBlocklist to '*' with an ExtensionInstallAllowlist of vetted IDs, or use ExtensionInstallForcelist) to remove the malicious-extension precondition - trade-off: users can no longer freely add extensions. You may also disable WebHID via DefaultWebHidGuardSetting (value 2 = block), which closes the vulnerable code path but breaks legitimate hardware integrations such as some security keys and peripherals. Refer to the advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html.