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

CVE-2026-10965 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.1%.

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

Google Chrome versions prior to 149.0.7827.53 contain a remote code execution vulnerability triggered when users visit malicious webpages, exposing all Chrome users across the organization to…. A patch is available.

How to fix or mitigate CVE-2026-10965?

24 hours: Inventory Chrome deployments and verify auto-update status; prepare patch rollout plan. 7 days: Deploy Chrome 149.0.7827.53 or later organization-wide; prioritize user-facing workstations and business-critical systems. 30 days: Verify 100% endpoint compliance with version 149.0.7827.53 or later; document any systems unable to patch and apply additional network-layer controls.

Google Chrome CVE-2026-10965

EUVD-2026-34414 HIGH

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

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

GHSA-46xr-wc9f-fxgc

Google RCE Red Hat Suse Chrome

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

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

SUSE

HIGH

qualitative

Red Hat

8.8 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Jun 05, 2026 - 02:57 vuln.today

CVSS changed

Jun 05, 2026 - 02:22 NVD

8.8 (HIGH)

CVE Published

Jun 04, 2026 - 23:16 nvd

UNKNOWN (no severity yet)

CVE Published

Jun 04, 2026 - 23:16 nvd

HIGH 8.8

DescriptionCVE.org

Integer overflow in DevTools in Google Chrome prior to 149.0.7827.53 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 versions prior to 149.0.7827.53 allows a remote attacker to execute arbitrary code inside the renderer sandbox by enticing a victim to visit a crafted HTML page that triggers an integer overflow in DevTools. Google has rated this Chromium issue as High severity and a vendor patch is available; no public exploit identified at time of analysis, and the bug is not currently listed in CISA KEV.

Technical ContextAI

The flaw resides in Chrome's DevTools subsystem and is classified as CWE-472 (External Control of Assumed-Immutable Web Parameter), manifesting as an integer overflow when handling values supplied via a crafted HTML page. Integer overflows in DevTools typically arise when untrusted size or index values from page content are used in arithmetic without bounds checking, producing wrapped values that subsequently corrupt memory operations in the renderer. Because exploitation occurs inside Chrome's sandbox, a successful exploit gains code execution in the renderer process but would still require a separate sandbox escape to achieve full host compromise - a common pairing in Chrome exploit chains. Affected CPE coverage centers on Google Chrome desktop builds below 149.0.7827.53 across supported platforms.

RemediationAI

Vendor-released patch: upgrade Google Chrome to 149.0.7827.53 or later on all desktop platforms per the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html, and force-restart browsers to ensure the new binary is loaded. Track downstream Chromium-based browsers (Microsoft Edge, Brave, Opera, Vivaldi) and Electron applications for corresponding security releases and update them as soon as patched builds are published. As a compensating control until patching completes, administrators can use enterprise policy to disable DevTools (DeveloperToolsAvailability = DeveloperToolsDisallowed) on managed endpoints, which removes the vulnerable surface but breaks legitimate developer workflows; additionally, browser isolation or strict site-blocking of untrusted destinations reduces exposure to attacker-controlled HTML at the cost of usability. Further context is available via the Chromium issue tracker entry https://issues.chromium.org/issues/511290038 (likely access-restricted until the disclosure window closes) and the NVD record https://nvd.nist.gov/vuln/detail/CVE-2026-10965.