CVE-2026-91739: Medium severity Google Chrome vulnerability
Chromium CVE-2026-91739: Missing authorization
Other sources
Missing authorization in Transactions Platform in Google Chrome prior to 153.0.8010.47 allowed a remote attacker who had compromised the renderer process to spoof UI elements via a crafted HTML page. (Chromium security severity: Medium)
— MITRE
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases](https://chromereleases.googleblog.com/2026)) for more information.
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 153.0.4234.46 - Upgrade
Upgrade
Google Chrome / Chromium-based browsersto a version that resolves this vulnerability.Fixed in 153.0.8010.47 - Compensating control
Mitigate by ensuring renderer-compromise scenarios are prevented/detected (since the issue is triggered after compromising the renderer process), e.g., harden the browser environment and monitor for renderer compromise indicators.
Event History
Frequently Asked Questions
What must an attacker achieve before this issue can be exploited?
The attacker must first compromise the Chrome renderer process. The spoofing issue is then triggered using a crafted HTML page.
Which Chrome versions should be remediated?
Google Chrome versions prior to 153.0.8010.47 are affected. Update Chrome to 153.0.8010.47 or later.
What is the practical impact after exploitation?
An attacker who has compromised the renderer can spoof UI elements, which could make malicious content appear to be legitimate browser or site interface elements.