CVE-2026-76044Network attack vector

Sandbox escape via USB state-change race

Published Aug 18, 2026 · Updated Aug 20, 2026

Sandbox escape in USB in Google Chrome before 151.0.7922.169 allows attackers to execute code outside the sandbox after renderer compromise. Chromium's USB DeviceImpl used browser-side blocking around device-wide and interface-specific state changes in a way that let USB operations race SetConfiguration, Reset, or targeted interface transitions against device state. Exploitation requires a separate renderer compromise and a crafted HTML page, so the flaw is a sandbox-escape stage rather than a standalone web-to-code bug.

CVSS severity8.3
High
EPSS probability0.39%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sandbox escape in USB in Google Chrome before 151.0.7922.169 allows attackers to execute code outside the sandbox after renderer compromise. Chromium's USB DeviceImpl used browser-side blocking around device-wide and interface-specific state changes in a way that let USB operations race SetConfiguration, Reset, or targeted interface transitions against device state. Exploitation requires a separate renderer compromise and a crafted HTML page, so the flaw is a sandbox-escape stage rather than a standalone web-to-code bug.

The record

CVE
CVE-2026-76044
Published
Aug 18, 2026
Updated
Aug 20, 2026
Vendor
Go standard library
Product
Google Chrome
Classifications
CWE-367, T1068
Attack vector
network
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=151.0.7922.169 <151.0.7922.169

What conditions does exploitation require?

Attack vectornetwork
Required privilegesUnavailable in this record.

What is affected?

Go standard library · Google Chromeversion=151.0.7922.169 <151.0.7922.169

Published CVSS scores

8.3CISA-ADPCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo