Sandbox escape via mismatched texture level validation
Published Nov 25, 2022 · Updated Oct 21, 2025
Heap buffer overflow in Google Chrome's GPU component before 107.0.5304.121 allows remote attackers to escape its sandbox via crafted HTML. Shared-image textures allocate one level, but the validating command decoder checks a target-derived maximum and lets a higher level index reach Texture::SetLevelCleared outside the level_infos vector. A victim must open the page, and exploitation requires control of the renderer process before GPU-process memory corruption can escape the sandbox.
Summary
What happened
Heap buffer overflow in Google Chrome's GPU component before 107.0.5304.121 allows remote attackers to escape its sandbox via crafted HTML. Shared-image textures allocate one level, but the validating command decoder checks a target-derived maximum and lets a higher level index reach Texture::SetLevelCleared outside the level_infos vector. A victim must open the page, and exploitation requires control of the renderer process before GPU-process memory corruption can escape the sandbox.
The record
- CVE
- CVE-2022-4135
- Published
- Nov 25, 2022
- Updated
- Oct 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1068, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 25, 2022CVE publishedPublication date reported by the CVE source.
- Oct 21, 2025Record 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=unspecified <107.0.5304.121
What conditions does exploitation require?
What is affected?
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
- Google Project Zero WebGL reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Google in-the-wild exploitation reportreported exploitation
- CISA Known Exploited Vulnerabilities catalog listingknown exploited catalog
- Renderer-to-GPU sandbox escape chainexploit chain
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