Sandbox escape via DevTools validation race
Published Jun 24, 2026 · Updated Jun 24, 2026
Input validation failure in Google Chrome's DevTools before 149.0.7827.197 allows remote attackers to escape the sandbox via crafted HTML. The public advisory identifies a race in DevTools but does not disclose the affected input or the invalid operation that crosses the sandbox boundary. Exploitation requires user interaction and prior renderer-process compromise; success grants execution beyond the renderer sandbox.
Summary
What happened
Input validation failure in Google Chrome's DevTools before 149.0.7827.197 allows remote attackers to escape the sandbox via crafted HTML. The public advisory identifies a race in DevTools but does not disclose the affected input or the invalid operation that crosses the sandbox boundary. Exploitation requires user interaction and prior renderer-process compromise; success grants execution beyond the renderer sandbox.
The record
- CVE
- CVE-2026-13025
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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.197 <149.0.7827.197
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