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

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

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

Google Chrome for Windows contains a sandbox escape vulnerability (CVE-2026-7343) that allows attackers who have compromised the browser renderer process to execute arbitrary code directly on the…. A patch is available.

How to fix or mitigate CVE-2026-7343?

Immediately identify all Google Chrome instances across Windows endpoints and document current version levels through your endpoint management system. Within seven days, deploy Chrome version 147.0.7727.138 or later across all affected Windows systems through your patch management tool, prioritizing development and test environments before broad production deployment. By day 30, complete patch deployment verification using patch compliance reporting, remediate any non-compliant systems, and formally document organizational remediation completion.

Google Chrome CVE-2026-7343

HIGH

Use After Free (CWE-416)

2026-04-28 Chrome

Denial Of Service Google Use After Free Memory Corruption Microsoft

7.5

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY

7.5 HIGH

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

vuln.today AI

7.5 HIGH

AC:H and the requirement of a pre-compromised renderer reflect a chained second-stage bug; UI:R for loading a crafted page; C/I/A:H for full browser-process code execution; S:U kept per vendor though a sandbox escape could argue S:C.

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

4.0 AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

HIGH

qualitative

Red Hat

9.0 HIGH

qualitative

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 24, 2026 - 03:58 vuln.today

Severity Changed

Apr 30, 2026 - 15:22 NVD

CRITICAL HIGH

CVSS changed

Apr 30, 2026 - 15:22 NVD

9.8 (CRITICAL) 7.5 (HIGH)

CVSS changed

Apr 29, 2026 - 13:23 NVD

9.8 (CRITICAL)

Patch released

Apr 29, 2026 - 00:30 nvd

Patch available

CVE Published

Apr 28, 2026 - 22:35 nvd

HIGH 7.5

DescriptionCVE.org

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

AnalysisAI

Sandbox escape in Google Chrome for Windows (versions prior to 147.0.7727.138) stems from a use-after-free in the Views UI component, allowing an attacker who has already compromised the renderer process to break out of the browser sandbox and gain broader code execution on the host via a crafted HTML page. Chromium rates the internal severity as Critical, though the assigned CVSS is 7.5 due to the high attack complexity and the renderer-compromise prerequisite. This is a second-stage bug: there is no public exploit identified at time of analysis, EPSS is very low (0.03%, 10th percentile), and it is not listed in CISA KEV.

Technical ContextAI

The flaw is a CWE-416 use-after-free in Chromium's 'Views' framework - the cross-platform C++ UI toolkit that Chrome uses to build and manage its window/widget hierarchy in the privileged browser process. Use-after-free occurs when code continues to reference a heap object after it has been freed, letting an attacker who controls heap layout reclaim that memory and steer execution. Because Views runs in the higher-privileged browser process (outside the renderer sandbox), corrupting it from a compromised renderer is a classic sandbox-escape primitive. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, with the fix landing in the Windows Stable channel at 147.0.7727.138.

RemediationAI

Vendor-released patch: update Google Chrome on Windows to 147.0.7727.138 or later via the Stable channel; restart the browser to complete the update since Chrome staged updates are not active until relaunch. The primary remediation is this upgrade - see https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_28.html and the tracking record at https://vuldb.com/vuln/360070. There is no configuration-level workaround for a memory-corruption bug in the browser process, but because exploitation requires a prior renderer compromise, defenders can reduce exposure by enforcing prompt auto-updates via enterprise policy, keeping Chrome's site isolation enabled (default), and using browser management/allowlisting to limit exposure to untrusted web content; note these are risk-reduction measures, not a substitute for the patch. For Chromium-based derivatives (Edge, and Red Hat/SUSE Chromium packages), apply the corresponding vendor rebuild once published.