Heap corruption via Inspector use-after-free
Published Mar 10, 2025 · Updated Feb 26, 2026
Use-after-free in Inspector in Google Chrome before 134.0.6998.88 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies a freed Inspector object as the memory-safety locus, but the restricted Chromium issue leaves the lifetime error and triggering object undisclosed. The target must render attacker-controlled HTML; public vendor material bounds the result to heap corruption and does not document code execution.
Summary
What happened
Use-after-free in Inspector in Google Chrome before 134.0.6998.88 allows remote attackers to trigger heap corruption via crafted HTML. Google identifies a freed Inspector object as the memory-safety locus, but the restricted Chromium issue leaves the lifetime error and triggering object undisclosed. The target must render attacker-controlled HTML; public vendor material bounds the result to heap corruption and does not document code execution.
The record
- CVE
- CVE-2025-2136
- Published
- Mar 10, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=134.0.6998.88 <134.0.6998.88
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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