Sandbox escape via incorrect WebUI authorization
Published Sep 15, 2026 · Updated Sep 15, 2026
Incorrect authorization in WebUI in Google Chrome before 153.0.8010.47 allows remote attackers to execute arbitrary code outside the sandbox. Google has not published which WebUI authorization decision is incorrect or how the crafted HTML page reaches the privileged browser process. Exploitation requires prior compromise of the renderer process; crossing that boundary permits arbitrary code execution beyond the renderer sandbox.
Summary
What happened
Incorrect authorization in WebUI in Google Chrome before 153.0.8010.47 allows remote attackers to execute arbitrary code outside the sandbox. Google has not published which WebUI authorization decision is incorrect or how the crafted HTML page reaches the privileged browser process. Exploitation requires prior compromise of the renderer process; crossing that boundary permits arbitrary code execution beyond the renderer sandbox.
The record
- CVE
- CVE-2026-91735
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1068
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 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=153.0.8010.47 <153.0.8010.47
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.
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