Skip to main content

Google Chrome CVE-2026-17846

| EUVDEUVD-2026-50595 MEDIUM
Origin Validation Error (CWE-346)
2026-07-30 Chrome GHSA-46c6-4cmr-4c64
Medium
Disputed · 6.5 Vendor: Chrome
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (Chrome) PRIMARY
6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
vuln.today AI
6.1 MEDIUM

AC:H reflects the mandatory renderer-compromise prerequisite; S:C captures that SOP bypass crosses origin security boundaries by definition.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
SUSE
CRITICAL
qualitative
Red Hat
7.9 MEDIUM
qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Chrome

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

Lifecycle Timeline

5
Analysis Generated
Jul 31, 2026 - 19:33 vuln.today
CVSS changed
Jul 31, 2026 - 19:22 NVD
6.5 (MEDIUM)
Patch available
Jul 30, 2026 - 02:02 EUVD
CVE Published
Jul 30, 2026 - 00:19 cve.org
MEDIUM 6.5
CVE Published
Jul 30, 2026 - 00:19 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

Inappropriate implementation in Media in Google Chrome on Windows prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to bypass same origin policy via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Same-origin policy bypass in Google Chrome for Windows (prior to 151.0.7922.72) allows a remote attacker who has already compromised the Chrome renderer process to circumvent cross-origin isolation controls via a crafted HTML page exploiting an origin validation flaw (CWE-346) in the Media component. This is a second-stage, chained exploitation capability - not a standalone entry point - requiring a prior renderer compromise to weaponize, which substantially constrains its independent risk. …

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
Identify Chrome on Windows target
Delivery
Deliver renderer RCE via separate exploit
Exploit
Gain code execution in sandboxed renderer
Execution
Serve crafted HTML triggering Media origin validation flaw
Persist
Bypass same-origin policy
Impact
Write or access cross-origin content in victim's browser

Vulnerability AssessmentAI

Exploitation Exploitation requires two stacked conditions: (1) the attacker must have already achieved code execution within Chrome's renderer process via a separate vulnerability; and (2) the victim must visit a crafted HTML page in Chrome on Windows prior to version 151.0.7922.72. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment CVSS 6.5 (Medium) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N indicates network-delivered, user-triggered, unauthenticated exploitation with high integrity impact and no scope change. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker first exploits a separate renderer RCE vulnerability to gain code execution inside Chrome's sandboxed renderer process on a Windows machine, then serves the victim a crafted HTML page that triggers the Media component's origin validation flaw, using the compromised renderer to bypass the same-origin policy and perform cross-origin writes - for example, injecting content into a banking session the victim has open in another tab. No public proof-of-concept code exists at time of analysis, so this scenario is theoretical but structurally plausible as part of a browser exploit chain.
Remediation Update Google Chrome for Windows to version 151.0.7922.72 or later, which contains the vendor-released patch per the stable channel advisory at http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. … Detailed patch versions, workarounds, and compensating controls in full report.

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

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Leap 16.0 Fixed
SUSE Package Hub 15 SP7 Affected

Share

CVE-2026-17846 vulnerability details – vuln.today

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