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

CVE-2026-13904 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:N/I:H/A:N. EPSS exploitation probability: 0.2%.

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

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

Chrome for iOS CVE-2026-13904

EUVD-2026-40590 MEDIUM

Protection Mechanism Failure (CWE-693)

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

GHSA-5r37-cpm2-c6pr

Authentication Bypass Google Apple Red Hat Suse

6.5

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

6.5 MEDIUM

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

vuln.today AI

6.5 MEDIUM

Network delivery with no privileges needed; user must visit crafted page (UI:R); only integrity impacted via navigation bypass, no confidentiality or availability effect.

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

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

SUSE

MEDIUM

qualitative

Red Hat

6.5 MEDIUM

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

High

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 18:29 vuln.today

CVSS changed

Jul 01, 2026 - 18:22 NVD

6.5 (MEDIUM)

CVE Published

Jun 30, 2026 - 23:17 cve.org

MEDIUM 6.5

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

Inappropriate implementation in Safe Browsing in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Navigation restriction bypass in Google Chrome's Safe Browsing implementation on iOS allows a remote, unauthenticated attacker to circumvent phishing and malicious-site protections via a specially crafted HTML page, affecting all Chrome for iOS versions prior to 150.0.7871.47. The flaw is classified as CWE-693 (Protection Mechanism Failure), meaning the Safe Browsing guard can be rendered ineffective rather than defeated through cryptographic or authentication means. No public exploit or CISA KEV listing has been identified, and the EPSS score of 0.23% (14th percentile) signals low current exploitation probability - but the zero-prerequisite network delivery and high integrity impact make this a meaningful risk for iOS users who have not updated.

Technical ContextAI

Google Safe Browsing is a threat-intelligence service integrated into Chrome that intercepts navigation events and compares target URLs against known malicious or phishing lists, blocking or warning before the browser proceeds. On iOS, Chrome's Safe Browsing stack operates under additional constraints imposed by WebKit and Apple's platform APIs, which can create divergent code paths from the desktop implementation. CWE-693 (Protection Mechanism Failure) indicates the flaw is not a memory corruption or logic error in the traditional sense but rather an incorrect implementation of the protection layer itself - for example, a code path where a crafted HTML page triggers a navigation flow that skips the Safe Browsing interstitial check entirely. The Chromium issue tracker reference (issues.chromium.org/issues/504185807) was filed against the iOS-specific Safe Browsing subsystem. The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N confirms the flaw requires no privileges and only network reachability plus user click, with the sole impact being integrity (navigation to otherwise-blocked destinations).

RemediationAI

Vendor-released patch: Chrome for iOS version 150.0.7871.47. Users should update Chrome on their iOS devices immediately via the Apple App Store. The advisory is published at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. If immediate update is not possible, a targeted compensating control is to use Safari (which has its own separate Safe Browsing implementation) for sensitive navigation or to configure enterprise mobile device management (MDM) policies to restrict Chrome access to known-safe URL allowlists. Note that MDM allowlisting imposes significant usability trade-offs for general-purpose browsing. Google's Enhanced Safe Browsing mode, if enabled, may provide additional layers of protection but does not eliminate the underlying flaw in standard Safe Browsing. The upstream Chromium issue tracking this fix is chromium.org/issues/504185807.