HIGH 7.8

CVE-2026-13778: Chrome WebUSB Use-After-Free RCE on macOS

A use-after-free vulnerability exists in Google Chrome's WebUSB implementation on macOS. When a user connects a malicious USB peripheral while Chrome is running, an attacker can trigger memory corruption that leads to arbitrary code execution with the privileges of the logged-in user. The flaw affects Chrome versions prior to 150.0.7871.47 on Mac systems and requires the user to interact with the malicious device; it cannot be exploited remotely.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.8 HIGH · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-416
Affected products
2 configuration(s)
Published / Modified
2026-06-30 / 2026-07-02

NVD description (verbatim)

Use after free in WebUSB in Google Chrome on Mac prior to 150.0.7871.47 allowed a local attacker to execute arbitrary code via a malicious peripheral. (Chromium security severity: Critical)

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-13778 is a use-after-free (CWE-416) vulnerability in the WebUSB subsystem of Google Chrome on macOS. The flaw occurs when WebUSB code references memory that has been freed, potentially allowing an attacker controlling a USB peripheral to craft inputs that trigger heap corruption. This memory safety issue can be leveraged to achieve code execution in the context of the Chrome browser process. The vulnerability was patched in Chrome 150.0.7871.47 on macOS.

Business impact

Organizations with macOS users who rely on Chrome and connect external USB peripherals face a direct risk of endpoint compromise. An attacker with physical access to a network-connected device or the ability to distribute a malicious USB device could gain code execution and establish a foothold on a user's machine. This is particularly concerning in environments where users connect untrusted USB devices, corporate premises with open device connectivity policies, or supply-chain scenarios where peripherals can be intercepted. The impact extends beyond individual machines if the compromised endpoint is used to access corporate networks or sensitive data.

Affected systems

Google Chrome on Apple macOS systems running versions prior to 150.0.7871.47 are vulnerable. This includes all patch levels of Chrome 149, 148, and earlier on macOS. Windows and Linux versions of Chrome are not affected. Older macOS versions and newer Chrome versions are in scope depending on the user's update status.

Exploitability

Exploitation requires local access to a target machine and the ability to connect a malicious USB peripheral. The attacker must craft a device that triggers the use-after-free condition when WebUSB interacts with it. While the vulnerability is not remotely exploitable, the barrier to entry is relatively low for an attacker with physical device placement capability. Social engineering to deliver a malicious peripheral (e.g., disguised as a promotional USB drive) is a realistic attack vector. User interaction is necessary—the USB peripheral must be connected while Chrome is active—but that interaction is passive and does not require any special action beyond acceptance of a device.

Remediation

Users should update Google Chrome to version 150.0.7871.47 or later on macOS. Administrators can enforce automatic updates via Chrome management policies or macOS device management tools. Until patching is complete, mitigating controls include restricting USB port access via physical locks or USB port disabling, blocking untrusted USB peripherals at the OS level through Gatekeeper or similar mechanisms, and limiting user privileges to reduce the impact of successful exploitation.

Patch guidance

Google has patched this vulnerability in Chrome 150.0.7871.47 for macOS. Users should check Settings > About Google Chrome to verify the installed version and trigger any pending updates. Organizations managing Chrome through enterprise policies (via Google Admin console or similar) should deploy the patched version through their managed rollout schedules. Verify patch deployment against Chrome's official release notes and the Chromium security advisory to confirm the exact fixed version for your deployment.

Detection guidance

Monitor for connections to untrusted USB devices, especially those that trigger WebUSB permissions dialogs or WebUSB-related Chrome crashes. Review Chrome crash reports and system logs for heap corruption indicators. Endpoint detection and response (EDR) tools should flag processes spawned from Chrome with unexpected privileges or behavior following USB device enumeration. Network telemetry should alert on suspicious outbound connections originating from Chrome processes that coincide with USB device insertion events. Canary tokens or honeypot USB devices can detect attacker reconnaissance in sensitive areas.

Why prioritize this

Although the vulnerability requires local access and user interaction, the combination of high CVSS score (7.8), critical Chromium severity rating, and realistic attack scenarios involving USB device distribution make this a significant risk. macOS systems are common in enterprise environments where users may connect peripherals, and successful exploitation grants full code execution. The lack of network barriers makes it an attractive target for physical-access attacks or supply-chain compromises. Prioritize patching in environments with high-value endpoints or lenient USB policies.

Risk score, explained

The CVSS 3.1 score of 7.8 (HIGH severity) reflects: local attack vector (AV:L) limiting remote exploitability but increasing risk for physically proximate attackers; low attack complexity (AC:L) meaning no special conditions are needed beyond device connection; no privilege requirement (PR:N); required user interaction (UI:R) in the form of connecting the peripheral; and high impact across confidentiality, integrity, and availability (C:H/I:H/A:H). The score appropriately penalizes the local-only nature while acknowledging the severity of arbitrary code execution.

Frequently asked questions

Can this vulnerability be exploited without physical access to a device?

No. CVE-2026-13778 requires local access to connect a malicious USB peripheral. It cannot be exploited remotely over a network. However, an attacker with physical access to a device or the ability to distribute a malicious USB peripheral (e.g., in a parking lot or via social engineering) can exploit it.

Does this affect Chrome on Windows or Linux?

No. This vulnerability is specific to macOS systems running Chrome versions prior to 150.0.7871.47. Chrome on Windows and Linux is not affected by this particular use-after-free in WebUSB.

What should organizations do if they cannot patch immediately?

Until patching is possible, enforce strict USB port access controls—disable unused USB ports, use physical locks, or deploy endpoint protection policies that block unauthorized USB devices. Monitor crash logs and USB device events for signs of exploitation. Consider implementing air-gapped or restricted network zones for critical users.

Is this vulnerability being exploited in the wild?

There is no indication that this vulnerability is currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, meaning active exploitation has not been widely confirmed at the time of publication. However, organizations should not rely on this as a reason to delay patching, as the attack vector is practical and the impact is severe.

This analysis is for informational purposes and reflects publicly available information as of the publication date. CVSS scores and vulnerability details are sourced from official CVE and vendor advisories. Organizations should verify patch versions and compatibility with their environments by consulting Google's official Chrome security updates and macOS release notes. This document does not constitute security advice or a guarantee of protection; consult your security team and vendor advisories before making deployment decisions. Exploit code or weaponized proof-of-concepts are not provided. Source: NVD (public-domain), retrieved 2026-08-09. Analysis generated by SEC.co (claude-haiku-4-5).