Sandbox escape via ANGLE out-of-bounds write
Published Aug 25, 2026 · Updated Aug 25, 2026
Out-of-bounds write in ANGLE in Google Chrome before 152.0.7977.65 on Windows allows remote attackers to execute code outside the sandbox. Google identifies ANGLE as the locus but has not published the affected function or the operation that miscalculates the write boundary; the linked issue remains restricted. Exploitation requires no prior privileges but requires a user to open crafted HTML, after which attacker-controlled code can run beyond the renderer sandbox.
Summary
What happened
Out-of-bounds write in ANGLE in Google Chrome before 152.0.7977.65 on Windows allows remote attackers to execute code outside the sandbox. Google identifies ANGLE as the locus but has not published the affected function or the operation that miscalculates the write boundary; the linked issue remains restricted. Exploitation requires no prior privileges but requires a user to open crafted HTML, after which attacker-controlled code can run beyond the renderer sandbox.
The record
- CVE
- CVE-2026-79138
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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=152.0.7977.65 <152.0.7977.65
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.
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