What is the CVSS score of EUVD-2026-34743?

EUVD-2026-34743 has a contested CVSS base score of 9.6 from a third party (e.g. CISA-ADP), while the vendor rates it Critical. vuln.today uses the vendor rating as authoritative.

Which versions of Google Chrome are affected by EUVD-2026-34743?

Google Chrome on Linux prior to version 149.0.7827.53 contains a sandbox escape vulnerability (CVSS 9.6) allowing unauthenticated remote attackers to execute arbitrary code through a crafted webpage.. A patch is available.

How to fix or mitigate EUVD-2026-34743?

Within 24 hours: Inventory Linux systems running Chrome and verify current versions. Within 7 days: Deploy Chrome version 149.0.7827.53 or later organization-wide. Within 30 days: Verify 100% remediation, document any non-compliant systems, and obtain risk acceptance from management for exceptions.

Google Chrome EUVD-2026-34743

| CVE-2026-11282 CRITICAL

Protection Mechanism Failure (CWE-693)

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

GHSA-gmvx-mxmx-j4x2

Information Disclosure Google

Critical

Disputed · 9.6 NVD

Severity by source

Sources disagree (Low–Critical)

NVD PRIMARY

9.6 CRITICAL

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

SUSE

CRITICAL

qualitative

Red Hat

0.0 LOW

qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 20:27 vuln.today

CVSS changed

Jun 05, 2026 - 20:22 NVD

9.6 (CRITICAL)

CVE Published

Jun 05, 2026 - 00:17 nvd

CRITICAL 9.6

CVE Published

Jun 05, 2026 - 00:17 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

Insufficient policy enforcement in Sandbox in Google Chrome on Linux prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)

AnalysisAI

Sandbox escape in Google Chrome on Linux prior to version 149.0.7827.53 allows remote attackers to potentially break out of the renderer sandbox via a crafted HTML page when a user visits an attacker-controlled site. The flaw stems from insufficient policy enforcement in the Linux sandbox implementation and carries a high CVSS of 9.6 due to scope change, though Chromium itself rates the security severity as Low. No public exploit identified at time of analysis, and EPSS is very low at 0.03%.

Technical ContextAI

Google Chrome employs a multi-process architecture in which untrusted web content is rendered inside a sandboxed process that, on Linux, relies on seccomp-bpf filters, user namespaces, and Chromium's setuid/namespace sandbox helpers to restrict syscalls and kernel attack surface. CWE-693 (Protection Mechanism Failure) indicates the sandbox's policy layer did not adequately enforce a restriction, allowing renderer-side code to reach resources or capabilities outside the sandbox boundary. The CPE/affected-version data narrows the issue specifically to Linux builds of Chrome prior to 149.0.7827.53, implying a platform-specific gap in policy enforcement rather than a cross-platform Chromium core bug.

RemediationAI

Upgrade Google Chrome on Linux to version 149.0.7827.53 or later, which is the vendor-released patch identified in the Chrome Releases stable-channel update at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. In managed environments, push the update via your endpoint management tooling and verify rollout by inspecting chrome://version on Linux clients. If patching is delayed, compensating controls include restricting browsing to trusted sites via enterprise policy (URLBlocklist/URLAllowlist), enabling Site Isolation (already on by default but verify chrome://flags#enable-site-per-process), and disabling renderer features unnecessary for the workload - recognizing that none of these defeat a successful sandbox escape and the only durable mitigation is the patch. Removing user-namespace support at the kernel level would break Chromium's sandbox entirely and is not recommended.