Heap corruption via Internals use after free
Published Nov 14, 2025 · Updated Feb 26, 2026
Use after free in Internals in Google Chrome on iOS before 127.0.6533.88 allows remote attackers to corrupt heap memory through curated UI gestures. Google identifies the locus only as Internals; the restricted issue does not disclose which object is freed or later dereferenced. Exploitation is unauthenticated but requires a user to perform a specific series of gestures, and successful heap corruption can compromise browser confidentiality, integrity, or availability.
Summary
What happened
Use after free in Internals in Google Chrome on iOS before 127.0.6533.88 allows remote attackers to corrupt heap memory through curated UI gestures. Google identifies the locus only as Internals; the restricted issue does not disclose which object is freed or later dereferenced. Exploitation is unauthenticated but requires a user to perform a specific series of gestures, and successful heap corruption can compromise browser confidentiality, integrity, or availability.
The record
- CVE
- CVE-2024-9126
- Published
- Nov 14, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 14, 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=127.0.6533.88 <127.0.6533.88
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