Skip to main content

Google Chrome CVE-2026-17902

| EUVDEUVD-2026-50651 LOW
Information Exposure (CWE-200)
2026-07-30 Chrome GHSA-3wq4-w788-rhg3
3.5
CVSS 3.1 · Vendor: Chrome
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker hosts crafted HTML page
  2. Delivery
    Victim on Linux Chrome visits page
  3. Exploit
    Victim interacts with page triggering Editing subsystem
  4. Execution
    Cross-origin data boundary bypassed
  5. Impact
    Limited cross-origin data exfiltrated to attacker

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation is limited to Google Chrome running on Linux - Chrome on Windows and macOS is not affected. The CVSS vector PR:L indicates the attacker requires some level of privilege or authenticated context (e.g., the victim must be logged into a service the crafted page can interact with, or the attacker controls a low-privilege origin). UI:R requires active victim interaction with a crafted HTML page - fully automated, drive-by exploitation without any user action is not possible. The confidentiality impact is Low (C:L), meaning only partial or limited cross-origin data is exposed rather than full session tokens or credential material. Non-Linux Chrome deployments are explicitly out of scope, and the interaction requirement prevents scripted mass exploitation.

Impact

All available signals converge on genuinely low priority. The CVSS base score is 3.5 (Low), driven by PR:L (requires some privilege), UI:R (requires victim interaction), S:U (no scope change), and C:L (limited confidentiality impact only). EPSS at 0.17% places this in the 7th percentile - statistically, fewer than 1 in 600 vulnerabilities at this score sees exploitation within 30 days. There is no CISA KEV listing and no public POC. The Linux platform restriction further reduces the realistic attacker surface relative to the full Chrome install base. The chromium security team itself rated this 'Low.' The only non-trivial signal is the network-accessible delivery vector (AV:N/AC:L), meaning a malicious web page is sufficient delivery - but this is neutralized by the required user interaction and authentication prerequisites. This is a patch-during-normal-cycle issue, not an emergency.

Exploit ScenarioDerived

An attacker hosts a crafted HTML page that triggers Chrome's Editing subsystem on a Linux host to inadvertently expose data from a cross-origin resource - for example, content from a tab or frame the victim is authenticated to. The victim must visit and actively interact with the attacker's page (e.g., clicking, selecting text, or pasting), after which limited cross-origin data is returned to the attacker. No public POC exists, making this attack currently theoretical in the absence of custom tooling.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 30, 2026

Cross-origin data leakage in Google Chrome on Linux (prior to 151.0.7922.72) stems from an inappropriate implementation in the browser's Editing subsystem, enabling a remote attacker to exfiltrate limited cross-origin information when a victim interacts with a crafted HTML page. The CVSS vector (PR:L/UI:R) confirms exploitation requires both some authenticated context and active victim interaction, materially reducing opportunistic risk. No public exploit has been identified and EPSS sits at the 7th percentile, consistent with the vendor's own 'Low' severity classification.

RemediationAI

Update Google Chrome on Linux to version 151.0.7922.72 or later via the stable channel, as detailed in the vendor advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome's built-in auto-update mechanism will apply this for most end users; enterprise deployments using managed policies should confirm the update has propagated. As a compensating control prior to patching, enabling Chrome's Strict Site Isolation (chrome://flags/#enable-site-per-process) can limit cross-origin data exposure by isolating renderer processes per origin, though this may increase memory usage. Given the Low severity, PR:L requirement, and user-interaction dependency, this fix is appropriate for inclusion in the next standard patch cycle rather than emergency deployment.

Affected VersionsENISA

Chrome 151.0.7922.72 <151.0.7922.72

Affected Packages

euvd chrome fix: 151.0.7922.72

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in Chromium's Editing component - the subsystem responsible for clipboard operations, text selection, drag-and-drop, and contenteditable handling - specifically on the Linux platform. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) identifies the root cause as a failure to enforce information boundaries: the editing subsystem improperly permits cross-origin data to become observable to an attacker-controlled page, violating the Same-Origin Policy. This is a platform-specific defect; the CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) applies broadly but the description explicitly scopes impact to Linux. The Chromium issue tracker entry (https://issues.chromium.org/issues/497251066) is the upstream reference for the root-cause defect.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Chrome) PRIMARY 3.5 LOW
AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
vuln.today AI 3.5 LOW

Network delivery via crafted HTML page justifies AV:N; PR:L reflects authenticated context needed for cross-origin leakage; UI:R for required victim interaction; C:L for limited data exposure only.

3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/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
Low
Privileges Required
Low
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

4
CVSS changed
Jul 30, 2026 - 14:37 NVD
3.5 (LOW)
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.5

DescriptionCVE.org

Inappropriate implementation in Editing in Google Chrome on Linux prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
High
Chrome is the dominant web browser across enterprise and consumer Linux deployments.
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

18
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +18
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Related Vulnerabilities in Google Chrome 151 Security Vulnerabilities

View all 80
CVE-2026-17895 MEDIUM
4.3
CVE-2026-17903 MEDIUM
5.4
CVE-2026-17910 MEDIUM
4.3
CVE-2026-17914 MEDIUM
5.3
CVE-2026-17919 MEDIUM
6.8
CVE-2026-17933 MEDIUM
4.3
CVE-2026-17941 MEDIUM
4.3
CVE-2026-17946 MEDIUM
6.5
CVE-2026-17949 MEDIUM
4.3
CVE-2026-17951 HIGH
8.8
CVE-2026-17953 MEDIUM
6.5
CVE-2026-17954 MEDIUM
4.3
CVE-2026-17965 MEDIUM
4.3
CVE-2026-17935 HIGH
8.8
CVE-2026-17948 HIGH
7.5
CVE-2026-17922 HIGH
8.8
CVE-2026-17947 CRITICAL
9.6
CVE-2026-17967 HIGH
8.8
CVE-2026-17894 HIGH
8.8
CVE-2026-17924 CRITICAL
9.6
CVE-2026-17950 HIGH
8.8
CVE-2026-17952 HIGH
7.5
CVE-2026-17956 HIGH
8.8
CVE-2026-17962 MEDIUM
6.1
CVE-2026-17940 CRITICAL
9.6
CVE-2026-17890 MEDIUM
5.8
CVE-2026-17891 MEDIUM
5.8
CVE-2026-17892 MEDIUM
6.5
CVE-2026-17893 MEDIUM
5.8
CVE-2026-17896 HIGH
7.5
CVE-2026-17897 MEDIUM
4.3
CVE-2026-17898 HIGH
7.5
CVE-2026-17899 HIGH
8.8
CVE-2026-17900 MEDIUM
4.3
CVE-2026-17901 MEDIUM
4.3
CVE-2026-17904 MEDIUM
4.3
CVE-2026-17905 MEDIUM
4.3
CVE-2026-17906 MEDIUM
5.8
CVE-2026-17907 MEDIUM
4.3
CVE-2026-17908 MEDIUM
5.8
CVE-2026-17909 MEDIUM
5.3
CVE-2026-17911 MEDIUM
4.3
CVE-2026-17912 MEDIUM
4.3
CVE-2026-17913 MEDIUM
5.4
CVE-2026-17915 MEDIUM
5.4
CVE-2026-17916 HIGH
7.5
CVE-2026-17917 MEDIUM
6.5
CVE-2026-17918 HIGH
8.8
CVE-2026-17920 HIGH
8.8
CVE-2026-17921 MEDIUM
6.5
CVE-2026-17923 MEDIUM
6.5
CVE-2026-17925 MEDIUM
4.3
CVE-2026-17926 MEDIUM
6.5
CVE-2026-17927 MEDIUM
4.3
CVE-2026-17928 MEDIUM
4.3
CVE-2026-17929 MEDIUM
6.5
CVE-2026-17930 HIGH
7.5
CVE-2026-17931 MEDIUM
6.5
CVE-2026-17932 MEDIUM
5.5
CVE-2026-17934 MEDIUM
4.3
CVE-2026-17936 MEDIUM
6.5
CVE-2026-17937 MEDIUM
4.3
CVE-2026-17938 MEDIUM
4.3
CVE-2026-17939 MEDIUM
4.3
CVE-2026-17942 MEDIUM
4.3
CVE-2026-17943 MEDIUM
4.3
CVE-2026-17944 MEDIUM
4.3
CVE-2026-17945 MEDIUM
4.3
CVE-2026-17955 MEDIUM
4.3
CVE-2026-17957 LOW
3.1
CVE-2026-17958 MEDIUM
4.3
CVE-2026-17959 MEDIUM
4.3
CVE-2026-17960 MEDIUM
4.3
CVE-2026-17961 MEDIUM
4.3
CVE-2026-17963 MEDIUM
4.3
CVE-2026-17964 MEDIUM
4.3
CVE-2026-17966 MEDIUM
6.2
CVE-2026-17968 MEDIUM
6.5
CVE-2026-17969 HIGH
8.8

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