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

CVE-2026-14006 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-14006?

Google Chrome contains a critical remote code execution vulnerability (CVE-2026-14006, CVSS 8.8) in the Navigation component that affects Desktop versions before 150.0.7871.47.. A patch is available.

How to fix or mitigate CVE-2026-14006?

Within 24 hours, inventory Chrome deployments across the organization and identify systems running versions prior to 150.0.7871.47, prioritizing developer workstations and systems with elevated privileges. Within 7 days, deploy Chrome 150.0.7871.47 or later organization-wide through your standard patch management process; communicate the update urgency to all users and consider enforcing automatic updates. Within 30 days, verify 100% deployment compliance through endpoint telemetry and audit logs to confirm no systems remain on vulnerable versions.

Google Chrome CVE-2026-14006

EUVD-2026-40694 HIGH

Use After Free (CWE-416)

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

GHSA-ch76-v6w4-9wx9

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

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-delivered crafted page needs no privileges but requires the victim to visit it (UI:R); memory-corruption RCE in the sandboxed renderer yields full C/I/A with no scope change.

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

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

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:17 cve.org

HIGH 8.8

DescriptionCVE.org

Use after free in Navigation 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: Medium)

AnalysisAI

Remote code execution in Google Chrome (Desktop) before 150.0.7871.47 stems from a use-after-free in the Navigation component, allowing a remote attacker who lures a victim to a crafted HTML page to corrupt memory and run arbitrary code in the renderer. Chromium rated it Medium, but the CVSS 8.8 reflects full C/I/A impact requiring only user interaction (visiting a page). There is no public exploit identified at time of analysis, and SSVC lists exploitation as none, with a low EPSS of 0.21%.

Technical ContextAI

The flaw is a CWE-416 use-after-free in Chrome's Navigation subsystem - the browser logic that manages page loads, session history, and document lifecycle transitions across frames. Such bugs occur when an object tied to a navigation (e.g., a frame, document, or navigation request) is freed while a dangling pointer to it is later dereferenced, typically triggered by carefully timed navigations or frame manipulations from attacker-controlled HTML/JavaScript. The affected software is Google Chrome per CPE cpe:2.3:a:google:chrome, and because Chromium is the upstream engine, the same defect class often propagates to other Chromium-based browsers (Edge, Brave, Opera) and to downstream distributors (the 'Suse' tag indicates SUSE packaging of Chromium). Google-reported (chrome-cve-admin@google.com), consistent with an internally-found memory-safety issue.

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.47 or later via the Stable channel and restart the browser to apply the fix, as described in the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); most installations auto-update, so verify the version under chrome://settings/help and force a relaunch in managed fleets. Users of Chromium-based browsers or distro Chromium packages (e.g., SUSE) should apply their vendor's corresponding update once it rebases to the patched Chromium. If patching must be delayed, reduce exposure by restricting browsing to trusted sites, enabling Enhanced Safe Browsing, and considering site isolation and strict enterprise policies to block untrusted external content - with the trade-off that these reduce but do not eliminate the risk of a crafted-page trigger and may hinder legitimate browsing.