Skip to main content

Google Chrome CVE-2026-17720

| EUVDEUVD-2026-50846 LOW
Origin Validation Error (CWE-346)
2026-07-30 Chrome GHSA-j795-4rhg-3gv3
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

AC:H reflects mandatory renderer pre-compromise; C:L only as cross-origin data disclosure is partial; no integrity or availability impact.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

4
Analysis Generated
Jul 30, 2026 - 19:50 vuln.today
Patch available
Jul 30, 2026 - 02:02 EUVD
CVE Published
Jul 30, 2026 - 00:19 cve.org
LOW 3.1
CVE Published
Jul 30, 2026 - 00:19 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

Insufficient policy enforcement in Passwords in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Cross-origin data leakage in Google Chrome's Passwords component (versions prior to 151.0.7922.72) enables a remote attacker who has already compromised the renderer process to exfiltrate password data across origin boundaries via a crafted HTML page. The root cause is insufficient policy enforcement (CWE-346: Origin Validation Error), meaning the browser's same-origin policy is not correctly applied within the Passwords subsystem when the renderer is already under attacker control. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Compromise renderer via separate Chrome vulnerability
Delivery
Craft malicious HTML page
Exploit
Deliver page to victim browser
Execution
Trigger password policy enforcement bypass
Impact
Leak cross-origin saved credential data

Vulnerability AssessmentAI

Exploitation Exploitation requires two distinct preconditions: first, the attacker must have already compromised the Chrome renderer process through a separate, independent vulnerability - this is explicitly stated in the CVE description ('remote attacker who had compromised the renderer process'). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N) yields a base score of 3.1 (Low), and the signal constellation fully supports this low urgency rating. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker who has already exploited a separate renderer-process vulnerability in Chrome (e.g., a V8 or Blink memory corruption bug) then serves the victim a crafted HTML page that leverages the insufficient policy enforcement in the Passwords component. The compromised renderer issues cross-origin credential requests that bypass origin validation, causing the Passwords subsystem to disclose saved credentials belonging to a different origin back to the attacker-controlled renderer context. …
Remediation The primary remediation is upgrading Google Chrome to version 151.0.7922.72 or later, which includes the vendor-released patch. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-17720 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy