Code execution via GPU heap buffer overflow
Published Apr 1, 2026 · Updated Apr 1, 2026
Heap buffer overflow in Google Chrome's GPU component before 146.0.7680.178 allows remote attackers to execute code via crafted HTML. Google identifies the GPU component and heap-overflow class, but the restricted issue does not disclose the affected function or unsafe operation. A user must load the crafted page; successful exploitation executes attacker-controlled code in the browser's security context.
Summary
What happened
Heap buffer overflow in Google Chrome's GPU component before 146.0.7680.178 allows remote attackers to execute code via crafted HTML. Google identifies the GPU component and heap-overflow class, but the restricted issue does not disclose the affected function or unsafe operation. A user must load the crafted page; successful exploitation executes attacker-controlled code in the browser's security context.
The record
- CVE
- CVE-2026-5272
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2026CVE publishedPublication date reported by the CVE source.
- Apr 1, 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=146.0.7680.178 <146.0.7680.178
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