Sandbox escape via Safe Browsing race
Published Jun 11, 2026 · Updated Jun 11, 2026
Race condition in Safe Browsing in Google Chrome before 149.0.7827.115 on macOS allows attackers to escape the sandbox via a malicious file. Google identifies the locus as Safe Browsing but has not disclosed which shared resource is raced or which unsynchronized operation mishandles the file. Exploitation requires prior compromise of the renderer process and processing of the malicious file; the resulting escape crosses Chrome's sandbox boundary.
Summary
What happened
Race condition in Safe Browsing in Google Chrome before 149.0.7827.115 on macOS allows attackers to escape the sandbox via a malicious file. Google identifies the locus as Safe Browsing but has not disclosed which shared resource is raced or which unsynchronized operation mishandles the file. Exploitation requires prior compromise of the renderer process and processing of the malicious file; the resulting escape crosses Chrome's sandbox boundary.
The record
- CVE
- CVE-2026-12022
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-362, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 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.115 <149.0.7827.115
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