Heap corruption via PowerVR object lifecycle misuse
Published Mar 4, 2026 · Updated Mar 4, 2026
Object lifecycle misuse in PowerVR in Google Chrome before 145.0.7632.159 allows remote attackers to corrupt heap memory via crafted HTML. The restricted issue record does not disclose the affected object or the incorrect lifecycle operation performed by PowerVR. User interaction is required to load the content, and the public record does not specify the attacker's capability after corruption.
Summary
What happened
Object lifecycle misuse in PowerVR in Google Chrome before 145.0.7632.159 allows remote attackers to corrupt heap memory via crafted HTML. The restricted issue record does not disclose the affected object or the incorrect lifecycle operation performed by PowerVR. User interaction is required to load the content, and the public record does not specify the attacker's capability after corruption.
The record
- CVE
- CVE-2026-3537
- Published
- Mar 4, 2026
- Updated
- Mar 4, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-787, CWE-1091, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2026CVE publishedPublication date reported by the CVE source.
- Mar 4, 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=145.0.7632.159 <145.0.7632.159
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
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