Sandbox escape via unmarked hidden target process
Published Jun 11, 2026 · Updated Jun 11, 2026
Sandbox escape in Google Chrome before 149.0.7827.115 allows remote attackers with a compromised renderer to cross the sandbox via crafted HTML. The Headless target handler creates a hidden target but fails to mark its associated renderer process as used, unlike regular Chrome. Exploitation requires prior renderer compromise and user interaction with the page; successful escape permits code to affect the host context beyond the renderer sandbox.
Summary
What happened
Sandbox escape in Google Chrome before 149.0.7827.115 allows remote attackers with a compromised renderer to cross the sandbox via crafted HTML. The Headless target handler creates a hidden target but fails to mark its associated renderer process as used, unlike regular Chrome. Exploitation requires prior renderer compromise and user interaction with the page; successful escape permits code to affect the host context beyond the renderer sandbox.
The record
- CVE
- CVE-2026-12027
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-693, CWE-250, T1203
- Attack vector
- network
- Privileges
- Unavailable
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