What is the CVSS score of EUVD-2026-40793?

EUVD-2026-40793 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 EUVD-2026-40793?

Google Chrome for Android versions before 150.0.7871.47 contain a sandbox escape vulnerability affecting all mobile users with the app installed.. A patch is available.

How to fix or mitigate EUVD-2026-40793?

Within 24 hours, inventory Chrome for Android deployments across managed Android devices and identify current versions in use. Within 7 days, push version 150.0.7871.47 or later to all devices through your mobile device management platform or app distribution system. Within 30 days, verify patch deployment success through compliance reports showing at least 95% of devices running the patched version, and close the tracking item once verified.

Google Chrome EUVD-2026-40793

| CVE-2026-14106 CRITICAL

Improper Input Validation (CWE-20)

2026-06-30 chrome-cve-admin@google.com

GHSA-43w3-j8j2-5xrc

Information Disclosure Google Red Hat

Critical

Disputed · 9.6 NVD

Severity by source

Sources disagree (Low–Critical)

NVD 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

Network-delivered via crafted page (AV:N, UI:R) but requires a pre-compromised renderer to chain, so AC:H; sandbox escape crosses trust boundary (S:C) with full browser-process impact.

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 VectorNVD

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 22, 2026 - 19:16 vuln.today

CVE Published

Jun 30, 2026 - 23:17 nvd

CRITICAL 9.6

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

DescriptionNVD

Insufficient validation of untrusted input in Text in Google Chrome on Android prior to 150.0.7871.47 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 150.0.7871.47 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page, exploiting insufficient input validation in the Text component. Chromium rated this Low severity because it is a second-stage bug requiring prior renderer compromise, and no public exploit has been identified. EPSS is low (0.17%, 7th percentile) and CISA SSVC records no known exploitation, so realistic urgency is far below the raw CVSS 9.6.

Technical ContextAI

The flaw lives in Chrome's Text handling within the Blink/Chromium rendering stack on Android and is classified as CWE-20 (Improper Input Validation). Chromium enforces a multi-process sandbox in which untrusted web content runs inside a low-privilege renderer isolated from the browser process and OS; a sandbox escape is the mechanism by which code confined to that renderer gains broader privileges. Insufficient validation of untrusted text input processed after a renderer is already under attacker control provides a path to cross the renderer-to-browser trust boundary. The single CPE provided, cpe:2.3:a:google:chrome:*, is generic and does not by itself scope the Android-specific, version-bounded impact described in the advisory.

RemediationAI

Vendor-released patch: update Google Chrome on Android to 150.0.7871.47 or later, which is delivered through the Google Play Store / Chrome stable channel; on managed Android fleets, push the update via MDM and confirm the client version. See the Chrome Releases advisory http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html and issue https://issues.chromium.org/issues/513532778. No standalone workaround neutralizes a sandbox-escape primitive, but because exploitation requires a prior renderer compromise, keeping the browser fully patched (closing the upstream renderer bugs that would be chained to this one) and enabling Enhanced Safe Browsing meaningfully raises the bar; on enterprise deployments, restricting untrusted browsing and enforcing site isolation reduces the odds an attacker ever reaches the compromised-renderer starting state, at the cost of some site-compatibility and performance overhead.