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

EUVD-2026-40472 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of Google Chrome are affected by EUVD-2026-40472?

Google Chrome versions prior to 150.0.7871.47 contain a remote code execution vulnerability in the Ozone platform layer that allows attackers to execute arbitrary code on user systems through crafted…. A patch is available.

How to fix or mitigate EUVD-2026-40472?

Within 24 hours: Verify Chrome auto-update status in your environment and identify deployment channels (Microsoft Update, MDM, manual). Within 7 days: Deploy Chrome version 150.0.7871.47 or later to all managed devices; ensure auto-update is enabled and send compliance notification to users on unmanaged devices. Within 30 days: Audit patch coverage reporting to confirm ≥95% adoption; address lagging devices and document any exclusions.

Google Chrome EUVD-2026-40472

| CVE-2026-13786 HIGH

Use After Free (CWE-416)

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

GHSA-jq2w-r287-vqvj

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

8.8

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

8.8 HIGH

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

vuln.today AI

8.8 HIGH

Network-reachable via a web page with no privileges but mandatory user interaction (UI:R); a Critical UAF yields high confidentiality, integrity, and availability impact within the browser process (S:U).

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

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

SUSE

HIGH

qualitative

Red Hat

9.6 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 17:36 vuln.today

CVSS changed

Jul 01, 2026 - 15:22 NVD

8.8 (HIGH)

CVE Published

Jun 30, 2026 - 23:16 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:16 cve.org

HIGH 8.8

DescriptionCVE.org

Use after free in Ozone in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

AnalysisAI

Remote code execution in Google Chrome's Ozone platform-abstraction layer prior to 150.0.7871.47 lets a remote attacker execute arbitrary code by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated Critical by Chromium and CVSS 8.8, requiring the victim to visit a malicious page (UI:R) but no privileges. No public exploit has been identified at time of analysis and EPSS probability is low (0.26%), but the memory-corruption class and 'total' technical impact make it a high-priority browser patch.

Technical ContextAI

Ozone is Chromium's graphics/windowing abstraction layer that mediates between the browser and the underlying platform's display, input, and GPU compositing subsystems (X11, Wayland, DRM/GBM, etc.). A use-after-free (CWE-416) occurs when the code continues to reference a heap object after it has been freed; an attacker who controls object lifetime and reallocation can reclaim the freed memory with attacker-shaped data, corrupt object vtables or pointers, and redirect execution. The single affected CPE is cpe:2.3:a:google:chrome (all versions below the fix), and because Ozone code runs inside the browser/GPU process, successful exploitation of the freed object can yield code execution in a Chrome process context, typically requiring a further sandbox escape for full system compromise.

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on all desktop platforms, per Google's Stable Channel Update advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); restart the browser to ensure the update is applied since Chrome staggers rollout. There is no supported feature-flag workaround for an Ozone UAF, so the practical compensating controls until deployment are behavioral: caution users against untrusted links, enforce update via enterprise policy (auto-update / forced relaunch), and consider Site Isolation and 'Enhanced Protection' Safe Browsing to raise the exploitation bar. For Chromium-derived browsers, apply the equivalent vendor build once released.