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

CVE-2026-10905 has a CVSS 3.1 base score of 8.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

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

Google Chrome contains a privilege escalation vulnerability affecting versions before 149.0.7827.53 that allows threat actors to break out of browser process isolation once they gain initial…. A patch is available.

How to fix or mitigate CVE-2026-10905?

Within 24 hours: Scan your infrastructure to identify all systems running Google Chrome below version 149.0.7827.53; assess deployment velocity and prioritize business-critical systems. Within 7 days: Deploy Google Chrome 149.0.7827.53 or later across all identified systems using your patch management system or automated update mechanism. Within 30 days: Validate patch deployment completeness using endpoint management tools to confirm no systems remain on vulnerable Chrome versions; document for compliance records.

Google Chrome CVE-2026-10905

EUVD-2026-34354 HIGH

Use After Free (CWE-416)

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

GHSA-597v-j4x4-vmv2

Denial Of Service Use After Free Memory Corruption Google Red Hat Suse Chrome

8.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.3 HIGH

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

SUSE

HIGH

qualitative

Red Hat

9.0 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 02:30 vuln.today

CVSS changed

Jun 05, 2026 - 02:22 NVD

8.3 (HIGH)

CVE Published

Jun 04, 2026 - 23:16 nvd

HIGH 8.3

CVE Published

Jun 04, 2026 - 23:16 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

Use after free in Network in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Sandbox escape in Google Chrome prior to 149.0.7827.53 allows a remote attacker who has already compromised the renderer process to break out of the sandbox via a use-after-free in the Network component, triggered by a crafted HTML page. Chromium rates the severity as High and a vendor patch is available; no public exploit identified at time of analysis.

Technical ContextAI

The flaw is a CWE-416 (Use After Free) memory corruption bug in Chrome's Network component, which handles network stack operations across the browser and renderer processes. Use-after-free conditions occur when memory is referenced after being freed, allowing an attacker who controls heap allocations to overwrite the freed object with attacker-controlled data and hijack subsequent dereferences. Because the bug resides in code reachable from the renderer-to-browser IPC boundary, successful exploitation can pivot a compromised renderer (S:C scope-changed in CVSS) into the more privileged browser process, defeating Chrome's site isolation sandbox. The affected codebase is Chromium-based, so downstream browsers (Edge, Brave, Opera, Vivaldi, Electron) likely inherit the same defect until they pick up the upstream fix.

RemediationAI

Vendor-released patch: Google Chrome 149.0.7827.53 (Stable channel) - upgrade all desktop Chrome installations immediately and verify via chrome://settings/help, referencing the advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. For managed fleets, push the update via enterprise update policies (Chrome Browser Cloud Management, Group Policy, MDM) and confirm rollout. Downstream Chromium browser users should apply vendor updates as soon as those projects merge the fix (tracked at https://issues.chromium.org/issues/487357841). No targeted workaround exists for a renderer-to-browser sandbox escape, but compensating controls include enabling site isolation (default), enforcing Enhanced Safe Browsing, disabling unneeded plugins/extensions that expand renderer attack surface, and for high-risk users enabling Chrome's Memory Safety / Site Isolation reporting and limiting browsing to trusted origins - trade-off is reduced compatibility and user friction.