Heap corruption via crafted HTML GPU processing
Published Feb 19, 2025 · Updated Feb 19, 2025
Heap buffer overflow in Google Chrome before 133.0.6943.126 allows remote attackers to corrupt GPU heap memory via crafted HTML. Google identifies the GPU component but has not published the faulty routine or unchecked memory operation because the issue record remains restricted. The attack requires a user to open the page; the public record identifies heap corruption but does not disclose a demonstrated post-corruption outcome.
Summary
What happened
Heap buffer overflow in Google Chrome before 133.0.6943.126 allows remote attackers to corrupt GPU heap memory via crafted HTML. Google identifies the GPU component but has not published the faulty routine or unchecked memory operation because the issue record remains restricted. The attack requires a user to open the page; the public record identifies heap corruption but does not disclose a demonstrated post-corruption outcome.
The record
- CVE
- CVE-2025-1426
- Published
- Feb 19, 2025
- Updated
- Feb 19, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 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=133.0.6943.126 <133.0.6943.126
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