Sandbox escape via Safe Browsing race
Published Jun 17, 2026 · Updated Jun 17, 2026
Race condition in Safe Browsing in Google Chrome before 149.0.7827.155 allows remote attackers to escape the browser sandbox via crafted HTML. Google has not disclosed the affected Safe Browsing code path or the competing operations that create the race, and the Chromium issue remains access-restricted. Exploitation requires user interaction and prior compromise of the renderer process; successful use crosses the macOS sandbox boundary under the browser user's host context.
Summary
What happened
Race condition in Safe Browsing in Google Chrome before 149.0.7827.155 allows remote attackers to escape the browser sandbox via crafted HTML. Google has not disclosed the affected Safe Browsing code path or the competing operations that create the race, and the Chromium issue remains access-restricted. Exploitation requires user interaction and prior compromise of the renderer process; successful use crosses the macOS sandbox boundary under the browser user's host context.
The record
- CVE
- CVE-2026-12454
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-362, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 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=149.0.7827.155 <149.0.7827.155
What conditions does exploitation require?
What is affected?
Published CVSS scores
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