Sandbox escape via forged error-page navigation
Published Sep 29, 2026 · Updated Sep 29, 2026
Incorrect authorization in Google Chrome on iOS before 154.0.8037.57 lets remote attackers with a compromised renderer escape the sandbox. The iOS navigation handler accepts a forged internal error-page URL without verifying that the browser initiated it, then permits navigation to privileged WebUI. Exploitation requires prior renderer compromise and delivery through a crafted HTML page; this flaw crosses the renderer sandbox boundary.
Summary
What happened
Incorrect authorization in Google Chrome on iOS before 154.0.8037.57 lets remote attackers with a compromised renderer escape the sandbox. The iOS navigation handler accepts a forged internal error-page URL without verifying that the browser initiated it, then permits navigation to privileged WebUI. Exploitation requires prior renderer compromise and delivery through a crafted HTML page; this flaw crosses the renderer sandbox boundary.
The record
- CVE
- CVE-2026-95355
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- WebM Project
- Product
- Google Chrome
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- unauthenticated
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?
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.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started