Windows sandbox escape via freed Views object
Published Apr 28, 2026 · Updated Apr 28, 2026
Use-after-free in Views in Google Chrome before 147.0.7727.138 allows remote attackers to escape the Windows sandbox via crafted HTML. The public record identifies Views as the memory-lifetime locus but does not disclose the object, function, or stale-access path. A victim must open the page after the attacker has compromised the renderer process; successful exploitation crosses the sandbox boundary.
Summary
What happened
Use-after-free in Views in Google Chrome before 147.0.7727.138 allows remote attackers to escape the Windows sandbox via crafted HTML. The public record identifies Views as the memory-lifetime locus but does not disclose the object, function, or stale-access path. A victim must open the page after the attacker has compromised the renderer process; successful exploitation crosses the sandbox boundary.
The record
- CVE
- CVE-2026-7343
- Published
- Apr 28, 2026
- Updated
- Apr 28, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2026CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=147.0.7727.138 <147.0.7727.138
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