Sandbox escape via DevTools reload race
Published Nov 14, 2025 · Updated Feb 26, 2026
Race condition in DevTools in Google Chrome before 126.0.6478.182 allows remote attackers to escape the browser sandbox via crafted HTML. Page.reload can reload an unintended target when its request races with navigation because the command does not bind the reload to the expected loader identifier. A user must open the page; successful exploitation breaks browser isolation and exposes host confidentiality, integrity, and availability.
Summary
What happened
Race condition in DevTools in Google Chrome before 126.0.6478.182 allows remote attackers to escape the browser sandbox via crafted HTML. Page.reload can reload an unintended target when its request races with navigation because the command does not bind the reload to the expected loader identifier. A user must open the page; successful exploitation breaks browser isolation and exposes host confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-7017
- Published
- Nov 14, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-362, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=126.0.6478.182 <126.0.6478.182
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