Code execution via Web Authentication use-after-free
Published Sep 9, 2026 · Updated Sep 10, 2026
Use after free in Google Chrome Web Authentication before 153.0.8010.36 allows remote attackers to execute code via crafted HTML. Google's public advisory identifies Web Authentication as the affected component but does not disclose the freed object's lifecycle or triggering operation. A user must open the crafted page; successful exploitation runs attacker-controlled code outside Chrome's sandbox.
Summary
What happened
Use after free in Google Chrome Web Authentication before 153.0.8010.36 allows remote attackers to execute code via crafted HTML. Google's public advisory identifies Web Authentication as the affected component but does not disclose the freed object's lifecycle or triggering operation. A user must open the crafted page; successful exploitation runs attacker-controlled code outside Chrome's sandbox.
The record
- CVE
- CVE-2026-87646
- Published
- Sep 9, 2026
- Updated
- Sep 10, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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=153.0.8010.36 <153.0.8010.36
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.
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