Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker hosts crafted HTML page with malicious CSS
-
DeliveryVictim lured via phishing or malicious redirect
-
ExploitChrome's CSS engine misprocesses input, triggering UXSS
-
ExecutionInjected script executes across victim's active browser origins
-
ImpactAttacker exfiltrates cross-origin session tokens or credentials
Vulnerability Assessment
| Weakness |
CWE
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a victim running Google Chrome on any desktop platform in a version prior to 151.0.7922.72 to visit an attacker-controlled HTML page containing malicious CSS - this single user navigation action (UI:R per CVSS) is the only prerequisite. No authentication to any service is required, no special browser configuration or feature flag needs to be enabled, and no server-side access to the victim's other web applications is needed. Exploitation is constrained by the user interaction requirement - the victim must be socially engineered or redirected to the crafted page - and is not automatable per SSVC assessment. The cross-origin impact (UXSS) is further limited to origins for which the victim has an active browser session at the time of exploitation. |
| Impact | The CVSS 6.1 Medium score with vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N reflects a network-reachable flaw with no privilege or configuration prerequisite, moderated by the requirement for user interaction (UI:R). The scope change (S:C) is the most consequential metric here - it signals that successful exploitation breaches the Same-Origin Policy, allowing the attacker's injected code to operate across victim origins, which is more dangerous than the partial C:L/I:L impact ratings suggest in isolation. EPSS at 0.20% (11th percentile) indicates very low observed exploitation probability at time of analysis, and SSVC independently confirms exploitation=none and automatable=no - meaning no current evidence of active or scripted mass exploitation. Together, these signals indicate a real but not emergency-tier priority: patch within the normal update cycle rather than via emergency change management. No conflicting signals identified across available intelligence sources. |
| Exploit ScenarioDerived | An attacker constructs a web page containing specially crafted CSS that triggers Chrome's inappropriate CSS implementation, bypassing Same-Origin Policy enforcement. The attacker lures a victim - via phishing, malicious advertisement, or compromised site redirect - to visit this page in an unpatched Chrome browser. Once loaded, the injected script executes in cross-origin contexts accessible to the browser session, allowing theft of authentication cookies, session tokens, or sensitive page content from other origins the victim has active sessions with. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 31, 2026
Universal Cross-Site Scripting (UXSS) in Google Chrome's CSS implementation enables a remote attacker to inject arbitrary scripts or HTML across origin boundaries by directing a victim to a crafted HTML page. All Chrome desktop versions prior to 151.0.7922.72 are affected. No public exploit has been identified at time of analysis and CISA SSVC rates exploitation as none, but the cross-origin scope change makes this meaningfully more impactful than a standard reflected XSS, warranting timely patching given Chrome's ubiquitous deployment footprint.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later, available via Chrome's built-in automatic update mechanism or the Chrome Releases blog at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Enterprise administrators managing Chrome through group policy or fleet management tools should deploy this version through their standard update pipeline. If immediate patching is not operationally feasible, restricting end-user navigation to untrusted or unknown web pages reduces exposure, though this imposes significant usability trade-offs and is not a substitute for patching. Enabling Chrome's Enhanced Safe Browsing mode provides partial protection against known malicious pages but does not remediate the underlying CSS implementation flaw. No configuration-level workaround that fully mitigates the vulnerability has been identified in available references.
Affected VersionsENISA
Affected Packages
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 flaw (CWE-79, Improper Neutralization of Input During Web Page Generation) resides in Chrome's CSS processing engine, where an inappropriate implementation allows attacker-controlled style data to escape normal origin isolation constraints. CSS-based UXSS attacks typically manipulate how the browser processes and applies stylesheet rules in ways that break the Same-Origin Policy, enabling injection of scripts into contexts belonging to other origins. The CVSS scope change (S:C) formally encodes this cross-origin boundary crossing. The affected product is identified via CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all desktop Chrome builds prior to the 151.0.7922.72 stable release. Chromium's security severity is rated Medium, consistent with the CVSS 6.1 base score.
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
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Network delivery via crafted page requires passive victim navigation (UI:R); UXSS cross-origin boundary crossing warrants scope change (S:C); no privileges or special config needed; no availability impact.
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
Lifecycle Timeline
3DescriptionCVE.org
Inappropriate implementation in CSS in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page. (Chromium security severity: Medium)
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Related Vulnerabilities in Google Chrome Multiple Security Flaws
View all 80Same weakness CWE-79 – Cross-site Scripting (XSS)
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-50746
GHSA-q345-5hjq-5q84
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB