What is the CVSS score of CVE-2026-17940?

CVE-2026-17940 has a contested CVSS base score of 9.6 from a third party (e.g. CISA-ADP), while the vendor rates it Critical. vuln.today uses the vendor rating as authoritative.

Which versions of Google Chrome are affected by CVE-2026-17940?

Google Chrome for Android before version 151.0.7922.72 contains a critical-rated sandbox escape in the Picture-in-Picture feature that allows attackers to break out of the renderer process.. A patch is available.

How to fix or mitigate CVE-2026-17940?

Within 24 hours, inventory Chrome for Android deployments and identify instances running versions before 151.0.7922.72. Within 7 days, begin user notification campaigns and enable automatic or forced updates to Chrome 151.0.7922.72 where organizational controls permit. Complete patching verification by day 30 and monitor for any exploitation attempts targeting renderer process vulnerabilities.

Google Chrome CVE-2026-17940

EUVD-2026-50866 CRITICAL

Improper Input Validation (CWE-20)

2026-07-30 Chrome

GHSA-xh92-v267-m4gm

Information Disclosure Google

Critical

Disputed · 9.6 Vendor: Chrome

Severity by source

Sources disagree (Low–Critical)

Vendor (Chrome) PRIMARY

9.6 CRITICAL

AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

vuln.today AI

8.3 HIGH

AC:H because a prior renderer compromise via a separate exploit chain is mandatory; UI:R and S:C retained; the sandbox escape yields high C/I/A across the browser-process boundary.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

4.0 AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

SUSE

CRITICAL

qualitative

Red Hat

0.0 LOW

qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Chrome

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 30, 2026 - 22:31 vuln.today

CVSS changed

Jul 30, 2026 - 20:37 NVD

9.6 (None) 9.6 (CRITICAL)

Patch available

Jul 30, 2026 - 02:02 EUVD

CVE Published

Jul 30, 2026 - 00:25 cve.org

CRITICAL 9.6

CVE Published

Jul 30, 2026 - 00:25 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

Insufficient validation of untrusted input in Picture-in-Picture in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)

AnalysisAI

Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox via crafted HTML delivered through the Picture-in-Picture feature. Chromium rates the severity Low and CISA SSVC exploitation is 'none', making this a second-stage bug in an exploit chain rather than a standalone entry point. No public exploit identified at time of analysis, and EPSS is low at 0.17% (7th percentile).

Technical ContextAI

The flaw resides in Chrome's Picture-in-Picture implementation, a Blink/renderer feature that pops video and increasingly arbitrary DOM content into a floating always-on-top window. The root cause is CWE-20 (Improper Input Validation): PiP consumes untrusted input from a page without sufficient validation, so a renderer already under attacker control can craft HTML that abuses this path to cross the renderer-to-browser sandbox boundary. The affected component per CPE is cpe:2.3:a:google:chrome, scoped by the description to the Android platform. Chrome's multi-process sandbox is designed so that a compromised renderer cannot reach OS resources or higher-privileged browser-process functionality; a sandbox escape like this defeats that containment.

RemediationAI

Vendor-released patch: 151.0.7922.72 - update Google Chrome for Android to 151.0.7922.72 or later via the Play Store, per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html); on managed fleets push the update through MDM and confirm the running build number. Because exploitation requires a pre-existing renderer compromise, the strongest compensating control until patched is to reduce renderer-compromise exposure by keeping the whole browser current and, where policy allows, limiting the Picture-in-Picture attack surface by disabling autoplay/PiP for untrusted sites - the trade-off is degraded video UX. Managed environments should enforce update timelines and block sideloaded or outdated Chrome builds. No workaround fully substitutes for the version upgrade, since the fix is in the browser binary itself.