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

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

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

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

Google Chrome CVE-2026-11219

EUVD-2026-34680 MEDIUM

Protection Mechanism Failure (CWE-693)

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

GHSA-65xm-4c6g-fw22

Authentication Bypass Google

4.3

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

4.3 MEDIUM

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

SUSE

MEDIUM

qualitative

Red Hat

5.4 LOW

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 15:28 vuln.today

CVSS changed

Jun 05, 2026 - 15:22 NVD

4.3 (MEDIUM)

CVE Published

Jun 04, 2026 - 23:17 nvd

UNKNOWN (no severity yet)

CVE Published

Jun 04, 2026 - 23:17 nvd

MEDIUM 4.3

DescriptionCVE.org

Inappropriate implementation in Navigation in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Low)

AnalysisAI

Navigation restriction bypass in Google Chrome prior to 149.0.7827.53 allows remote unauthenticated attackers to circumvent Chrome's built-in navigation controls by delivering a crafted HTML page to a victim. The flaw stems from an inappropriate implementation in Chrome's Navigation subsystem (CWE-693: Protection Mechanism Failure), yielding low integrity impact with no confidentiality or availability consequences. No public exploit has been identified at time of analysis and EPSS exploitation probability is 0.02% (4th percentile), consistent with Google Chromium's own Low severity classification for this issue.

Technical ContextAI

The vulnerability resides in Chrome's Navigation component - the subsystem responsible for enforcing same-origin policies, content security policies, and other navigation-based access controls that govern where and how web pages can direct browser navigation. CWE-693 (Protection Mechanism Failure) classifies this as a case where an existing security control was not correctly implemented, allowing an attacker to route around it rather than defeating it cryptographically or through memory corruption. The affected product is Google Chrome for desktop on all supported platforms at versions prior to 149.0.7827.53, as confirmed by the Chrome stable channel advisory and ENISA EUVD-2026-34680. No CPE strings were included in the source intelligence; the affected version range is derived from the NVD description and EUVD affected-version field ('Chrome < 149.0.7827.53'). The issue was reported through chrome-cve-admin@google.com, indicating internal or coordinated disclosure through Google's standard security pipeline.

RemediationAI

Upgrade Google Chrome to version 149.0.7827.53 or later; this is the vendor-released patch confirmed by the Chrome stable channel update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's built-in silent auto-update mechanism will deliver this fix automatically on most managed and consumer desktop deployments - administrators should verify fleet compliance via endpoint management tooling. As a compensating control prior to patch deployment, organizations can use web proxy content filtering or Chrome enterprise browser policies to restrict navigation to untrusted or arbitrary external HTML content, though this introduces operational friction in open-browsing environments. Given the low severity (integrity-only, user-interaction-required impact), delayed patching carries limited risk, but routine update cadence remains the definitive remediation with no meaningful trade-offs.