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

CVE-2026-14024 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.2%.

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

Google Chrome on Linux is vulnerable to heap corruption that could allow remote attackers to crash the browser or potentially execute code after tricking users to visit a malicious webpage and…. A patch is available.

How to fix or mitigate CVE-2026-14024?

Within 24 hours: Inventory Chrome deployments on Linux systems and identify user populations. Within 7 days: Deploy Chrome version 150.0.7871.47 or later enterprise-wide using auto-update settings, managed deployment tools, or targeted user notifications. Within 30 days: Verify patch deployment success via browser telemetry and confirm >95% of managed Chrome instances are running version 150.0.7871.47 or later.

Google Chrome CVE-2026-14024

EUVD-2026-40712 HIGH

Use After Free (CWE-416)

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

GHSA-2x2m-wp42-98x6

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

Remote crafted page (AV:N), no privileges (PR:N) but mandatory user gestures (UI:R); UAF heap corruption in the browser process yields full C/I/A within an unchanged scope.

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:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

HIGH

qualitative

Red Hat

8.8 MEDIUM

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 - 15:31 vuln.today

CVSS changed

Jul 01, 2026 - 15:22 NVD

8.8 (HIGH)

CVE Published

Jun 30, 2026 - 23:17 cve.org

HIGH 8.8

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Use-after-free in Google Chrome's Ozone component on Linux prior to 150.0.7871.47 lets a remote attacker trigger heap corruption after luring a user to a crafted HTML page and inducing specific UI gestures. Rated CVSS 8.8 with high confidentiality, integrity and availability impact, it is patched in the stable channel but requires user interaction (UI:R). No public exploit is identified at time of analysis and EPSS exploitation probability is low (0.21%, 11th percentile), and Google classifies the Chromium severity as Medium.

Technical ContextAI

Ozone is Chromium's platform abstraction layer that mediates windowing, display, and input/graphics backends (e.g., X11, Wayland, DRM) on Linux, translating browser rendering and UI-gesture handling into native surface operations. The root cause is CWE-416 (Use After Free): an object in Ozone is freed while a pointer to it is still retained, so a subsequent UI-driven code path dereferences dangling memory, producing heap corruption. In browsers, controlled reallocation of the freed region combined with the corrupted heap state is the classic primitive attackers chain toward arbitrary read/write and potentially code execution within the affected process.

RemediationAI

Vendor-released patch: update Google Chrome on Linux to 150.0.7871.47 or later via the stable channel, then fully restart the browser to load the new binary; enterprise fleets should push the update through their managed Chrome/repository channel and verify the running version. See the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Until the update is applied, reduce exposure by avoiding untrusted web pages and not performing prompted UI gestures on unfamiliar sites; because the bug is in the Ozone Linux graphics/UI layer there is no clean feature toggle, but organizations can gate the rollout window with network/web filtering to limit exposure to attacker-controlled pages - noting this only reduces, not eliminates, risk and does not substitute for the patch.