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

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

Google Chrome versions prior to 150.0.7871.46 contain a critical remote code execution vulnerability in the V8 JavaScript engine (CVE-2026-14430, CVSS 8.8) that allows attackers to execute arbitrary…. A patch is available.

How to fix or mitigate CVE-2026-14430?

Within 24 hours: Issue organization-wide advisory instructing employees to avoid visiting untrusted websites and update Chrome when prompted; confirm IT patch readiness and supply chain access to version 150.0.7871.46. Within 7 days: Deploy Chrome 150.0.7871.46 to all managed endpoints via Group Policy, WSUS, or Chrome Enterprise Management (CEM); enforce automatic updates for unmanaged instances. Within 30 days: Audit patch deployment across 100% of managed and BYOD-enrolled systems; enable continuous monitoring for Chrome version compliance and collect metrics for executive reporting.

Google Chrome CVE-2026-14430

EUVD-2026-41174 HIGH

External Control of Assumed-Immutable Web Parameter (CWE-472)

2026-07-01 Chrome

GHSA-9r75-hh5f-2vjg

RCE Google Red Hat Suse

8.8

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) 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 needs no auth (PR:N) but requires the user to open it (UI:R); high C/I/A reflect renderer RCE, scope unchanged as impact stays within the sandbox.

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 HIGH

qualitative

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

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 02, 2026 - 02:24 vuln.today

CVSS changed

Jul 02, 2026 - 02:22 NVD

8.8 (None) 8.8 (HIGH)

CVE Published

Jul 01, 2026 - 22:21 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 01, 2026 - 22:21 cve.org

HIGH 8.8

DescriptionCVE.org

Integer overflow in V8 in Google Chrome prior to 150.0.7871.46 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Remote code execution in Google Chrome's V8 JavaScript engine (versions prior to 150.0.7871.46) allows a remote attacker to run arbitrary code inside the renderer sandbox by luring a victim to a crafted HTML page. The flaw is an integer overflow in V8, rated High by Chromium and scored CVSS 8.8; exploitation requires user interaction (visiting a malicious page) but no authentication. There is no public exploit identified at time of analysis, and CISA SSVC records exploitation status as none, indicating no observed in-the-wild activity yet.

Technical ContextAI

V8 is the C++ JavaScript and WebAssembly engine that powers Chrome and all Chromium-derived browsers, compiling and executing untrusted script from any visited web page. The root cause is an integer overflow - an arithmetic operation whose result exceeds the bounds of its integer type, producing an incorrect (often undersized) value that is subsequently used for memory sizing or indexing, leading to out-of-bounds access and attacker-controllable memory corruption. Note the reported weakness classification CWE-472 (External Control of Assumed-Immutable Web Parameter) does not align with an integer overflow, for which CWE-190 would be the conventional class; this appears to be a mislabeled CWE and should be verified against the Chromium issue tracker. The affected CPE is cpe:2.3:a:google:chrome:*, i.e. the Chrome desktop browser; because Chromium is the upstream, Edge, Brave, Opera, Vivaldi and Electron-based apps embedding the same V8 build are likely affected downstream.

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.46 or later on all desktop platforms via the Stable channel, then fully restart the browser so the new V8 build is loaded (per https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html). In managed environments, force the update through enterprise policy/auto-update and confirm the version at chrome://settings/help. Apply corresponding updates to Chromium-based browsers as their vendors ship them. There is no configuration-based workaround for a V8 engine flaw; as interim compensating controls before patching you can disable the browser's JavaScript JIT (via the 'V8 optimizer' / --js-flags='--no-opt' or site-isolation-friendly hardening) to shrink the attack surface - this reduces performance and may break some web apps - and restrict browsing to trusted sites, but these only lower risk and are not a substitute for the fixed version.