Sandbox-escape code execution via Verifier use-after-free
Published Sep 29, 2026 · Updated Sep 29, 2026
Use-after-free in Google Chrome's Verifier before 154.0.8037.57 allows remote attackers to execute code outside the sandbox via network traffic. Google identifies Verifier as the affected component but has not disclosed the object lifecycle or exact operation that accesses freed memory. Exploitation requires an already compromised renderer process; network traffic alone is not identified as sufficient.
Summary
What happened
Use-after-free in Google Chrome's Verifier before 154.0.8037.57 allows remote attackers to execute code outside the sandbox via network traffic. Google identifies Verifier as the affected component but has not disclosed the object lifecycle or exact operation that accesses freed memory. Exploitation requires an already compromised renderer process; network traffic alone is not identified as sufficient.
The record
- CVE
- CVE-2026-95354
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- WebM Project
- Product
- Google Chrome
- Classifications
- CWE-416, T1068
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 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=154.0.8037.57 <154.0.8037.57
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started