Sandbox escape via incorrect USB authorization
Published Aug 25, 2026 · Updated Aug 25, 2026
Incorrect authorization in Google Chrome's USB component before 152.0.7977.65 allows remote attackers to execute code outside the sandbox. Google identifies the locus only as USB and has not published which authorization decision incorrectly accepts attacker-controlled input. Exploitation requires a compromised renderer, a crafted HTML page, and social engineering; successful exploitation escapes the browser sandbox.
Summary
What happened
Incorrect authorization in Google Chrome's USB component before 152.0.7977.65 allows remote attackers to execute code outside the sandbox. Google identifies the locus only as USB and has not published which authorization decision incorrectly accepts attacker-controlled input. Exploitation requires a compromised renderer, a crafted HTML page, and social engineering; successful exploitation escapes the browser sandbox.
The record
- CVE
- CVE-2026-78911
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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.
- Affected versionversion=152.0.7977.65 <152.0.7977.65
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Weakness, pattern, technique
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