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

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

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

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

Google Chrome CVE-2026-17715

EUVD-2026-50841 LOW

Origin Validation Error (CWE-346)

2026-07-30 Chrome

GHSA-4qjg-8r9v-c734

Information Disclosure Google

3.1

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY

3.1 LOW

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

vuln.today AI

3.1 LOW

Network delivery via crafted page (AV:N), high complexity from required specific UI gestures (AC:H), no attacker auth needed (PR:N), mandatory victim interaction (UI:R), limited confidentiality-only impact with no scope change.

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

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

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 30, 2026 - 19:54 vuln.today

Patch available

Jul 30, 2026 - 02:02 EUVD

CVE Published

Jul 30, 2026 - 00:19 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 30, 2026 - 00:19 cve.org

LOW 3.1

DescriptionCVE.org

Inappropriate implementation in Passwords in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who convinced a user to engage in specific UI gestures to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Cross-origin data leakage in Google Chrome's Passwords feature prior to version 151.0.7922.72 allows a remote attacker to read cross-origin data by convincing a victim to perform specific UI gestures on a crafted HTML page. Rated High severity by the Chromium security team - higher than the NVD CVSS base score of 3.1 suggests - reflecting the sensitivity of credential-adjacent cross-origin boundary violations. No public exploit identified at time of analysis, and SSVC assessment confirms no current exploitation activity.

Technical ContextAI

CWE-346 (Origin Validation Error) identifies the root cause: the Passwords subsystem in Chrome fails to properly enforce same-origin policy boundaries under specific UI-interaction conditions. The affected component is Chrome's built-in password manager and autofill implementation, covering all desktop platform variants as indicated by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*. The flaw allows a crafted page hosted on one origin to infer or read data - likely credential metadata, autofill signals, or password presence indicators - belonging to a different origin, directly violating the browser's isolation model. The CVSS vector (S:U) confirms no sandbox escape is involved; the impact is bounded to the browser process itself.

RemediationAI

Update Google Chrome to version 151.0.7922.72 or later, which resolves this vulnerability per the Chrome stable channel advisory at http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome updates automatically for most users; enterprise administrators should verify deployment via policy management tools (e.g., Google Admin Console or Chromium enterprise policies). As a compensating control for environments unable to update immediately, disabling Chrome's built-in password manager via enterprise policy (PasswordManagerEnabled=false) eliminates the vulnerable code path entirely, though this removes autofill functionality and may lead users toward less secure credential storage alternatives - weigh this trade-off before applying.