Sandbox escape via Navigation policy failure
Published Aug 6, 2026 · Updated Aug 6, 2026
Sandbox escape in Google Chrome before 151.0.7922.109 allows remote attackers to cross the browser security boundary via crafted HTML. The Navigation component insufficiently enforces an undisclosed policy after renderer compromise; Google keeps the underlying bug details restricted. Exploitation requires user interaction with the page and prior renderer compromise, after which the attacker gains capabilities outside the renderer sandbox.
Summary
What happened
Sandbox escape in Google Chrome before 151.0.7922.109 allows remote attackers to cross the browser security boundary via crafted HTML. The Navigation component insufficiently enforces an undisclosed policy after renderer compromise; Google keeps the underlying bug details restricted. Exploitation requires user interaction with the page and prior renderer compromise, after which the attacker gains capabilities outside the renderer sandbox.
The record
- CVE
- CVE-2026-19152
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-693, T1203
- 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.
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