Sandboxed arbitrary code execution
Published Aug 6, 2026 · Updated Aug 6, 2026
Inappropriate implementation in V8 in Google Chrome before 151.0.7922.109 allows remote attackers to execute code inside the sandbox. Google identifies the affected locus only as V8; the restricted issue record does not disclose the implementation error or operation performed on crafted HTML. Exploitation requires a user to open a crafted HTML page, and the published impact is code execution within Chrome's sandbox rather than a sandbox escape.
Summary
What happened
Inappropriate implementation in V8 in Google Chrome before 151.0.7922.109 allows remote attackers to execute code inside the sandbox. Google identifies the affected locus only as V8; the restricted issue record does not disclose the implementation error or operation performed on crafted HTML. Exploitation requires a user to open a crafted HTML page, and the published impact is code execution within Chrome's sandbox rather than a sandbox escape.
The record
- CVE
- CVE-2026-19168
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-693, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=151.0.7922.109 <151.0.7922.109
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