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

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

Google Chrome versions before 150.0.7871.47 contain a sandbox escape vulnerability in media capture functionality that permits attackers with pre-existing renderer process compromise to break browser…. A patch is available.

How to fix or mitigate EUVD-2026-40730?

24 hours: Identify and inventory all Chrome installations currently running versions before 150.0.7871.47 in your fleet; escalate findings to endpoint owners. 7 days: Deploy Chrome 150.0.7871.47 or later across all managed endpoints; ensure auto-update policies are enabled to prevent regression. 30 days: Validate 100% deployment compliance through asset inventory; document patch deployment completion.

Google Chrome EUVD-2026-40730

| CVE-2026-14043 CRITICAL

Use After Free (CWE-416)

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

GHSA-fff7-xvg4-9wc8

Denial Of Service Google Use After Free Memory Corruption Red Hat Suse

Critical

Disputed · 9.6 Vendor: google

Severity by source

Sources disagree (Low–Critical)

Vendor (google) 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 exploitation is chained and requires a pre-existing renderer compromise plus specific media-path grooming; UI:R for the crafted page, S:C and C/I/A:H for a full sandbox escape.

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

5.1 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: google

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 01, 2026 - 14:28 vuln.today

CVSS changed

Jul 01, 2026 - 14:22 NVD

9.6 (CRITICAL)

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:17 cve.org

CRITICAL 9.6

DescriptionCVE.org

Use after free in GetUserMedia in Google Chrome 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's GetUserMedia (media capture) implementation before version 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. The flaw is a use-after-free (CWE-416) reported by Google's own security team; despite an NVD CVSS of 9.6, Chromium rates its severity Low, and there is no public exploit identified at time of analysis with an EPSS of only 0.17% (7th percentile).

Technical ContextAI

The vulnerability lives in Chrome's GetUserMedia code path, the Web API (navigator.mediaDevices.getUserMedia) that brokers access to camera and microphone streams between the sandboxed renderer and the more-privileged browser process. The root cause is a use-after-free (CWE-416): an object tied to a media-capture request is freed while a reference to it remains reachable, letting subsequently controlled memory be reused and manipulated. Because GetUserMedia handling crosses the renderer/browser IPC boundary, a UAF here is a candidate primitive for corrupting browser-process memory, which is why it is characterized as a sandbox-escape rather than a renderer-only bug. The affected component is the Chromium/Blink media stack shared across all Chromium-based desktop builds (cpe would map to cpe:2.3:a:google:chrome).

RemediationAI

Vendor-released patch: Google Chrome 150.0.7871.47 - update to this version or later via Chrome's built-in updater (Help > About Google Chrome) and relaunch the browser so the new binary loads, which is the complete fix and has no functional trade-off. In managed fleets, push the update through your enterprise update policy/MDM and force a browser restart to ensure the patched process is running. Users of other Chromium-based browsers should apply their vendor's build that incorporates the Chromium fix once available. As an interim compensating control, because the flaw is reached through the media-capture API you can restrict or block camera/microphone access via enterprise policy (e.g., set DefaultMediaStreamSetting/VideoCaptureAllowed/AudioCaptureAllowed to blocked), which reduces the GetUserMedia attack surface at the cost of breaking legitimate video-conferencing and voice web apps. Reference advisory: https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html.