Sandbox escape via Metrics object lifecycle error
Published Jun 17, 2026 · Updated Jun 17, 2026
Object lifecycle error in Google Chrome Metrics before 149.0.7827.155 allows remote attackers to escape the sandbox via crafted HTML. The Chromium issue tracker restricts the underlying Metrics bug, so the precise object and incorrect lifecycle operation are not public. Exploitation requires prior renderer-process compromise and user interaction with the crafted page; successful escape crosses Chrome's renderer sandbox boundary.
Summary
What happened
Object lifecycle error in Google Chrome Metrics before 149.0.7827.155 allows remote attackers to escape the sandbox via crafted HTML. The Chromium issue tracker restricts the underlying Metrics bug, so the precise object and incorrect lifecycle operation are not public. Exploitation requires prior renderer-process compromise and user interaction with the crafted page; successful escape crosses Chrome's renderer sandbox boundary.
The record
- CVE
- CVE-2026-12465
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 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=149.0.7827.155 <149.0.7827.155
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.
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