Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts malicious HTML page exploiting Paint side-channel
-
DeliveryVictim is lured to visit page in unpatched Chrome
-
ExploitPage JavaScript observes rendering timing or state variations
-
ExecutionCross-origin resource content inferred from side-channel signals
-
ImpactSensitive cross-origin data exfiltrated to attacker
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Hardware access control bypass
|
| Exploitation Conditions | Exploitation requires a victim user to actively visit an attacker-controlled HTML page in an unpatched version of Google Chrome (prior to 150.0.7871.47) on a desktop platform. The CVSS vector confirms user interaction is required (UI:R) and that no attacker authentication or privileges are needed (PR:N). Impact is strictly limited to cross-origin confidentiality leakage - no code execution, no write capability, and no availability disruption. Exploitation is further constrained by the passive, observational nature of side-channel attacks, which typically require careful calibration to a target's rendering behavior. No special browser configuration, feature flag, or non-default setting is referenced as a prerequisite. The key limiting factors are the UI:R gate (victim must visit the page) and the absence of any integrity or availability vector. |
| Impact | The CVSS 3.1 score of 6.5 (Medium) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N reflects a high confidentiality impact accessible over the network with no attacker privileges, but critically gated by required user interaction. The EPSS score of 0.21% (11th percentile) signals very low near-term exploitation probability, aligning with the absence of this CVE from CISA KEV and the lack of any referenced public exploit code. The High confidentiality rating is technically accurate - cross-origin data leakage can expose session tokens, private page content, or authentication state - but real-world exploitation requires both a willing victim to visit an attacker-controlled page AND a precise side-channel implementation, making mass exploitation unlikely. There is no integrity or availability impact. Risk is elevated specifically for users routinely accessing sensitive cross-origin resources (corporate intranets, banking portals) in the same browser session as untrusted web content. For most environments, this is a routine patch-cycle priority rather than an emergency response item. |
| Exploit ScenarioDerived | An attacker hosts a crafted HTML page that embeds or references cross-origin resources and uses JavaScript to observe timing or state variations in Chrome's Paint rendering subsystem while those resources are rendered. When a victim visits this page in an unpatched Chrome browser, the side-channel allows the attacker script to infer pixel-level or structural content belonging to a different origin - potentially including session-authenticated pages loaded in adjacent tabs or frames. No public exploit code has been identified at time of analysis, and the attack requires active victim participation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 01, 2026
Side-channel cross-origin data leakage in Google Chrome's Paint rendering component (all versions prior to 150.0.7871.47) allows remote attackers to infer sensitive content belonging to other origins by enticing a victim to visit a crafted HTML page. The vulnerability exploits a weakness in the Paint subsystem's rendering pipeline (CWE-1300: Improper Protection of Physical Side Channels), enabling an attacker page to observe rendering state or timing variations and reconstruct protected cross-origin data. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; EPSS probability is low at 0.21% (11th percentile). Vendor-released patch is available in Chrome 150.0.7871.47.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later, which contains the vendor-released patch for this vulnerability per the Chrome Stable Channel Update advisory at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Chrome's built-in auto-update mechanism should apply this automatically on most managed and consumer deployments; administrators should verify fleet compliance via endpoint management tooling. For environments where immediate patching is delayed, consider enforcing cross-origin isolation headers (Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp) on sensitive web applications to reduce the surface available to a leaking attacker page - note this may break third-party integrations that rely on cross-origin resource sharing. Restricting Chrome usage on endpoints that simultaneously access untrusted sites and sensitive intranet resources is an additional compensating measure, though operationally disruptive. These controls do not eliminate the underlying Paint side-channel and do not substitute for patching.
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 vulnerability is rooted in Chrome's Paint subsystem - the component responsible for rasterizing and compositing web content to screen within the Blink rendering engine. CWE-1300 (Improper Protection of Physical Side Channels) covers scenarios where an implementation inadvertently exposes information through observable side effects of computation, such as rendering timing differences, pixel state leakage, or compositing order signals. In browser contexts, this class of flaw has historically manifested as pixel-stealing attacks, cross-origin timing oracles, or GPU-level state leakage that allows a page to infer content rendered by a different origin. The affected CPE-level product is Google Chrome desktop, all builds prior to 150.0.7871.47, as confirmed by EUVD-2026-40608. The Chromium security team internally classified severity as Medium, consistent with the constrained, read-only nature of the impact.
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
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Network-delivered via crafted page requiring active victim visit (UI:R, PR:N); impact is read-only cross-origin data leakage with no integrity or availability consequence (C:H/I:N/A:N).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Side-channel information leakage in Paint in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to leak cross-origin data 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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-40608
GHSA-7m6q-ggf5-rwg4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB