EUVD-2026-50866
GHSA-xh92-v267-m4gm
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted page
-
DeliveryCompromise renderer via chained bug
-
ExploitAbuse Picture-in-Picture input validation
-
ExecutionEscape Chrome sandbox
-
ImpactGain browser-process privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Requires an attacker who has ALREADY compromised the Chrome renderer process on Android - this is a sandbox-escape primitive, not an initial-access bug. The concrete trigger is a crafted HTML page abusing the Picture-in-Picture feature's insufficient input validation. The platform is limited to Google Chrome on Android below 151.0.7922.72, and some user interaction is required (CVSS UI:R). Limiting factors: the mandatory prior renderer compromise (so a full exploit chain, typically a second memory-corruption bug, is needed first), the user-interaction requirement, and the version/platform constraint. These are precisely why Chromium rates it Low and SSVC marks Exploitation 'none' despite the 9.6 base score. |
| Impact | The signals conflict sharply and must be read carefully. The published CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R, S:C, C:H/I:H/A:H = 9.6) reads as a near-critical remote flaw, but the description and Chromium's own 'Low' rating tell a different story: exploitation REQUIRES an already-compromised renderer process, so it is not directly reachable by a raw remote attacker and only matters as a link in a larger chain. SSVC confirms this posture - Exploitation: none, Automatable: no, Technical Impact: total. EPSS is low (0.17%, 7th percentile), there is no CISA KEV listing, and no known POC. The 'total' technical impact is genuine (full sandbox escape) but is gated behind the hard precondition of renderer compromise, so the PR:N/AC:L scoring materially overstates standalone risk - CVSS indicates an unauthenticated network vector while the description clearly implies a prior renderer compromise; verify with vendor context. Net: a legitimate defense-in-depth fix worth patching promptly, not an internet-facing 9.6-grade emergency on its own. Also note the input Tags list 'Information Disclosure' whereas the real impact is a sandbox escape (a code-execution boundary crossing) - treat that tag as unreliable. |
| Exploit ScenarioDerived | A victim on Android visits an attacker-controlled page that first compromises Chrome's renderer through a separate memory-safety bug, and the same crafted HTML then abuses Picture-in-Picture's insufficient input validation to escape the sandbox into the more-privileged browser process. Some user interaction is involved (UI:R). No public POC is known, and this step only functions as the second stage of a multi-bug chain. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
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).
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.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
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.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Sources disagree (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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.
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
Lifecycle Timeline
4DescriptionCVE.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)
Executive ViewAI
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. However, this vulnerability functions as a second-stage attack requiring prior renderer process compromise, and no public exploit code has been identified. Organizations should prioritize patching Android users but may deprioritize relative to single-stage entry vectors.
Apply vendor patch: update Chrome for Android to version 151.0.7922.72 or later.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in Google Chrome 151 Security Vulnerabilities
View all 80Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Exploit-DB