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

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

A memory safety vulnerability in Google Chrome (versions before 150.0.7871.47) could allow attackers to execute code on user systems through malicious websites.. A patch is available.

How to fix or mitigate CVE-2026-14107?

Within 24 hours: Identify all Chrome installations and current version distribution across the organization. Within 7 days: Deploy Chrome 150.0.7871.47 or later using enterprise push mechanisms; enable auto-update for unmanaged endpoints. Within 30 days: Audit deployment completion and document patch status in the asset inventory system.

Google Chrome CVE-2026-14107

EUVD-2026-40794 HIGH

Use After Free (CWE-416)

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

GHSA-r265-xc9c-pww5

Memory Corruption Google Denial Of Service Use After Free RCE 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 needs a victim visit (AV:N/UI:R), no privileges (PR:N), and sandboxed RCE yields high C/I/A with scope unchanged (S:U) since the host is not directly compromised.

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

Primary rating from Vendor (google).

CVSS VectorVendor: google

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

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

CVSS changed

Jul 01, 2026 - 15:22 NVD

8.8 (HIGH)

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 Scheduling in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Low)

AnalysisAI

Remote code execution in Google Chrome desktop before 150.0.7871.47 stems from a use-after-free in the Scheduling component, letting a remote attacker run arbitrary code within the renderer sandbox when a victim opens a crafted HTML page. There is no public exploit identified at time of analysis and the vulnerability is not in CISA KEV; EPSS is low at 0.21% (12th percentile). …

Unlock full vulnerability intelligence

Risk assessment & exploitation conditions
Attack chain visualization
Remediation with exact patch versions
Threat intelligence from 22 sources
Personal watchlist & email alerts

Continue with Google Continue with GitHub

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access

Lure victim to crafted HTML page

Delivery

JavaScript grooms renderer heap

Exploit

Trigger use-after-free in Scheduling

Execution

Reclaim freed object with controlled data

Impact

Execute arbitrary code within sandbox

Access

Lure victim to crafted HTML page

Delivery

JavaScript grooms renderer heap

Exploit

Trigger use-after-free in Scheduling

Execution

Reclaim freed object with controlled data

Impact

Execute arbitrary code within sandbox

Vulnerability AssessmentAI

Exploitation	Exploitation requires the victim to actively open or be redirected to an attacker-controlled HTML page in a vulnerable Chrome build (CVSS UI:R confirms required user interaction); no authentication or prior privileges are needed (PR:N). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment	Signals conflict and must be weighed carefully. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario	An attacker hosts a malicious web page (or injects a malicious ad/iframe into a legitimate site) that uses JavaScript to trigger the use-after-free in Chrome's Scheduling code. When a victim running a vulnerable Chrome build visits the page, the attacker gains arbitrary code execution inside the renderer sandbox. …
Remediation	Vendor-released patch: 150.0.7871.47 - upgrade Chrome to 150.0.7871.47 or later by allowing Chrome's built-in auto-update to complete and fully relaunching the browser (updates do not take effect until restart), or push the fixed build via enterprise management (Google Update/ADMX policies). … Detailed patch versions, workarounds, and compensating controls in full report.