EUVD-2026-40542
GHSA-pvhv-2c87-949v
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Requires a pre-compromised renderer (PR:L) and user interaction (UI:R) at high complexity (AC:H); escaping the renderer sandbox into the browser process is a scope change (S:C) with high C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in Speech in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Privilege escalation in Google Chrome for Android before 150.0.7871.47 lets an attacker who has already compromised the renderer process break out further by feeding a crafted HTML page into the Speech component, which fails to validate untrusted input (CWE-20). Google rated it Medium severity; a fix has shipped in the Stable channel, EPSS is low (0.21%, 11th percentile), and there is no public exploit identified at time of analysis. This is a sandbox-escape-class chaining bug rather than a standalone remote drive-by, since it presupposes a prior renderer compromise.
Technical ContextAI
The flaw sits in Chromium's Speech subsystem (the Web Speech API surface that brokers speech recognition/synthesis between the sandboxed renderer and higher-privilege browser-process code) on the Android build of Chrome. The root cause is CWE-20, Improper Input Validation: data crossing the renderer-to-browser trust boundary through the Speech IPC/mojo interface is insufficiently validated, so a malicious renderer can supply values the browser process wrongly trusts. Chromium's multi-process model relies on treating the renderer as untrusted; any browser-process code that accepts renderer-controlled input without strict validation becomes a privilege-escalation vector, which is exactly the pattern here. The affected component is identified in the Chromium issue tracker entry (issues.chromium.org/issues/508092634).
RemediationAI
Vendor-released patch: update Google Chrome for Android to 150.0.7871.47 or later, per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); on Android this arrives through Google Play, so ensure automatic app updates are enabled and force-update managed fleets via MDM. There is no component-level workaround documented by the vendor, but because exploitation requires a compromised renderer, the practical compensating control is to reduce renderer-compromise exposure - restrict browsing to trusted sites, keep the browser fully patched against renderer RCE bugs, and in managed environments enforce Site Isolation and disable unneeded web features; note that broadly disabling speech/microphone features via enterprise policy would degrade Web Speech API functionality for users and does not fully close the input-validation path. Prioritize simply upgrading, as the patched build is already available.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today