Skip to main content
Vulnerability Database/CVE-2026-95335

CVE-2026-95335: Google Chrome HID Use After Free Vulnerability

CVE-2026-95335 is a use after free vulnerability in Google Chrome HID that enables attackers to escape the sandbox and execute arbitrary code. This article covers the technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-95335 Overview

CVE-2026-95335 is a use-after-free vulnerability in the Human Interface Device (HID) component of Google Chrome. The flaw affects Chrome versions prior to 154.0.8037.57. An attacker who has already compromised the renderer process can leverage this bug to execute arbitrary code outside the browser sandbox. Exploitation requires user interaction with a crafted HTML page. The vulnerability is tracked under CWE-416 and is rated High severity by the Chromium security team.

Critical Impact

Successful exploitation allows a remote attacker to escape the Chrome renderer sandbox and execute code in the browser process, breaking a core browser security boundary.

Affected Products

  • Google Chrome for Desktop versions prior to 154.0.8037.57
  • Chromium-based browsers incorporating the vulnerable HID implementation
  • Systems running affected Chrome builds on Windows, macOS, and Linux

Discovery Timeline

  • 2026-09-29 - CVE-2026-95335 published to the National Vulnerability Database
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-95335

Vulnerability Analysis

The vulnerability resides in Chrome's HID subsystem, which brokers communication between web content and USB or Bluetooth Human Interface Devices through the WebHID API. A use-after-free condition occurs when the HID component references memory after that memory has been released. An attacker who controls a compromised renderer can trigger the freed object path and reuse the dangling reference to influence execution flow in a more privileged process.

Because the affected code runs outside the renderer sandbox boundary, successful exploitation results in a sandbox escape. This chain typically follows an initial renderer compromise from a separate memory corruption bug delivered through a crafted HTML page.

Root Cause

The defect is a classic use-after-free ([CWE-416]) in the HID component. Object lifetime management fails to synchronize with in-flight IPC or callback handling. When the HID object is destroyed while a reference is still held, subsequent operations dereference freed memory. See the Chromium Issue Tracker #555299641 for additional details.

Attack Vector

Exploitation requires two conditions. First, the attacker must already control the renderer process, typically through a prior browser exploit. Second, the victim must load or interact with a crafted HTML page that drives the vulnerable HID code path. The compromised renderer then sends malicious IPC messages that trigger the free-and-reuse sequence in the browser process, enabling code execution outside the sandbox.

No public proof-of-concept exploit is currently available, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.

Detection Methods for CVE-2026-95335

Indicators of Compromise

  • Chrome browser processes spawning unexpected child processes or shell interpreters after visiting untrusted web content
  • Anomalous WebHID API activity from sites that have no legitimate hardware interaction requirement
  • Crashes in the Chrome browser process referencing the HID component in crash telemetry

Detection Strategies

  • Inventory endpoints for Chrome versions earlier than 154.0.8037.57 using software asset management data
  • Correlate browser process crashes with subsequent process creation events to identify sandbox escape attempts
  • Baseline WebHID API usage across the environment and alert on unusual invocations from newly visited domains

Monitoring Recommendations

  • Monitor Chrome parent-child process relationships for deviations from expected browser behavior
  • Collect and forward Chrome crash reports to a central telemetry system for triage
  • Track outbound network connections initiated by Chrome subprocesses to catch post-exploitation staging

How to Mitigate CVE-2026-95335

Immediate Actions Required

  • Update Google Chrome to version 154.0.8037.57 or later on all managed endpoints
  • Restart Chrome after the update to ensure the patched binary is loaded into memory
  • Verify patch deployment across the fleet using centralized software inventory tooling

Patch Information

Google addressed this vulnerability in the Stable channel release documented in the Google Chrome Release Notes. Users on Chrome versions at or above 154.0.8037.57 are no longer affected. Chromium-based browser vendors should pull the corresponding upstream fix from the Chromium Issue Tracker #555299641.

Workarounds

  • Disable the WebHID API through enterprise policy where hardware device access is not required for business functions
  • Restrict Chrome extension installations and untrusted site access via managed browser policies until patching completes
  • Apply site isolation and enforce enhanced Safe Browsing protections to reduce initial renderer compromise risk
bash
# Enterprise policy example to disable WebHID via Chrome policy
# Linux: /etc/opt/chrome/policies/managed/webhid_policy.json
{
  "DefaultWebHidGuardSetting": 2,
  "WebHidBlockedForUrls": ["*"]
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.