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

EUVD-2026-34399 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 EUVD-2026-34399?

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

Google Chrome iOS EUVD-2026-34399

| CVE-2026-10950 MEDIUM

Protection Mechanism Failure (CWE-693)

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

GHSA-8hvh-cj39-g625

Information Disclosure Google Apple

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:H/I:N/A:N

SUSE

MEDIUM

qualitative

Red Hat

8.8 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

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:37 vuln.today

CVSS changed

Jun 05, 2026 - 20:22 NVD

6.5 (MEDIUM)

CVSS changed

Jun 05, 2026 - 20:22 NVD

6.5 (MEDIUM)

CVE Published

Jun 04, 2026 - 23:16 nvd

MEDIUM 6.5

CVE Published

Jun 04, 2026 - 23:16 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

Insufficient policy enforcement in Autofill in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Cross-origin data leakage in Google Chrome on iOS (versions prior to 149.0.7827.53) stems from insufficient policy enforcement in the Autofill component, enabling a remote unauthenticated attacker to read sensitive cross-origin data by directing a victim to a crafted HTML page. The CVSS score of 6.5 (Medium) reflects high confidentiality impact with no integrity or availability loss; the attack requires user interaction but no attacker privileges. EPSS probability sits at 0.03% (11th percentile), SSVC reports no current exploitation, and the CVE is absent from CISA KEV, collectively indicating low real-world threat urgency despite the medium severity classification.

Technical ContextAI

The vulnerability resides in the Autofill subsystem of Google Chrome specifically on iOS platforms. CWE-693 (Protection Mechanism Failure) identifies the root cause: the browser's same-origin policy enforcement within the Autofill feature was insufficiently applied, permitting a malicious page to probe or extract data that should be strictly isolated to a different origin. This class of flaw arises when a user-convenience feature - here, automated form filling - inadvertently exposes data across security boundaries because its internal policy checks do not fully replicate the browser's core cross-origin restrictions. The iOS-specific scoping suggests this may relate to platform-specific integration between Chrome and iOS WKWebView or native iOS Autofill APIs, as distinct from the behavior of desktop Chromium builds. Autofill is enabled by default in Chrome on iOS, making the vulnerable code path available in standard configurations.

RemediationAI

Update Google Chrome on iOS to version 149.0.7827.53 or later - this is the vendor-released patch confirmed by EUVD-2026-34399 and the Chrome Releases advisory at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Updates should be applied via the Apple App Store. If an immediate update is operationally constrained, a targeted compensating control is to disable the Autofill feature in Chrome on iOS (iOS Settings > Chrome > disable AutoFill and Passwords), which removes the vulnerable code path at the cost of losing autofill convenience for users. No additional workarounds beyond patching or Autofill disablement are indicated by the available data. Note that the URL in the advisory references 'desktop' - administrators should confirm the iOS release channel update announcement separately if managing a fleet of iOS Chrome deployments.