Sandboxed code execution via V8 race
Published Aug 13, 2025 · Updated Feb 26, 2026
Race condition in V8 in Google Chrome before 139.0.7258.127 allows remote attackers to execute code in the sandbox via a crafted HTML page. Google identifies the affected locus only as V8 and keeps the underlying issue details restricted, so the racing operations and corrupted state are undisclosed. A target must load the attacker-controlled page; the published impact is code execution inside Chrome's sandbox, not a documented sandbox escape.
Summary
What happened
Race condition in V8 in Google Chrome before 139.0.7258.127 allows remote attackers to execute code in the sandbox via a crafted HTML page. Google identifies the affected locus only as V8 and keeps the underlying issue details restricted, so the racing operations and corrupted state are undisclosed. A target must load the attacker-controlled page; the published impact is code execution inside Chrome's sandbox, not a documented sandbox escape.
The record
- CVE
- CVE-2025-8880
- Published
- Aug 13, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-362, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 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=139.0.7258.127 <139.0.7258.127
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