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

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

Is there a patch available for CVE-2026-11045?

Yes, a patch is available for CVE-2026-11045. Update the affected software to the latest version immediately.

Google Chrome CVE-2026-11045

EUVD-2026-34494 MEDIUM

Improper Input Validation (CWE-20)

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

GHSA-g53g-7mpf-pxm6

Information Disclosure Google Chrome

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

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

SUSE

MEDIUM

qualitative

Red Hat

5.0 MEDIUM

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 20:45 vuln.today

CVSS changed

Jun 05, 2026 - 20:22 NVD

6.5 (MEDIUM)

CVE Published

Jun 04, 2026 - 23:17 nvd

MEDIUM 6.5

CVE Published

Jun 04, 2026 - 23:17 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

Insufficient validation of untrusted input in GPU in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Memory disclosure in Google Chrome's GPU component (versions prior to 149.0.7827.53) enables a remote attacker who has already compromised the renderer process to read sensitive data from process memory by delivering a crafted HTML page. The vulnerability stems from insufficient validation of untrusted input passed to the GPU subsystem, classified as CWE-20 (Improper Input Validation), and is rated Medium severity by the Chromium security team despite a CVSS Confidentiality impact of High - reflecting that successful exploitation requires a prior renderer compromise as a prerequisite. No public exploit code has been identified and EPSS probability stands at just 0.05% (15th percentile), indicating low current exploitation likelihood.

Technical ContextAI

The affected component is Chrome's GPU process, which operates as a separate privilege boundary within Chrome's multi-process architecture. The GPU process handles rendering commands from the renderer process; insufficient validation of renderer-supplied input (CWE-20) allows an already-compromised renderer to craft inputs that cause the GPU process to disclose out-of-bounds or otherwise sensitive memory. This is architecturally significant: Chrome's sandbox model separates the renderer, GPU, and browser processes specifically to limit the blast radius of renderer compromises, so this vulnerability represents a partial breakdown of that inter-process trust boundary. Affected product per ENISA EUVD (EUVD-2026-34494): Google Chrome versions below 149.0.7827.53 across all supported desktop platforms.

RemediationAI

Update Google Chrome to version 149.0.7827.53 or later via the browser's built-in update mechanism (Menu > Help > About Google Chrome) or through enterprise deployment tooling. The vendor-released patch is confirmed by the Chrome stable channel update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. As a compensating control for environments where immediate patching is not feasible, restricting access to untrusted web content via DNS filtering or web proxies reduces exposure, though this does not eliminate the underlying flaw. Enabling Chrome's Enhanced Safe Browsing mode limits delivery of malicious pages but does not block the vulnerability class. Enterprises may also consider disabling GPU hardware acceleration (--disable-gpu flag) as a temporary workaround, but this significantly degrades browser performance and rendering quality and is not recommended long-term.