Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessVictim visits crafted HTML page
-
DeliveryPage embeds cross-origin resource
-
ExploitAnimation side channel measures discrepancy
-
ExecutionInfer cross-origin data
-
ImpactLeak limited cross-origin information
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V6 - Authentication Timing-safe comparisons
|
| Exploitation Conditions | Exploitation requires the victim to actively load an attacker-controlled HTML page (UI:R) that embeds cross-origin content and triggers the Animation observable-discrepancy side channel. The key LIMITING factors are: high attack complexity (AC:H) because the attacker must exploit a timing/rendering discrepancy that typically needs favorable conditions and repeated measurement to extract usable data; the impact is confined to a limited cross-origin information leak (C:L, I:N, A:N) with no code execution, data modification, or denial of service; and the victim must be running a Chrome version prior to 155.0.8059.39. No special non-default browser configuration is required. |
| Impact | This is a low-priority, low-real-risk issue despite being a browser vulnerability in an ubiquitous product. The CVSS 3.1 base score is 3.1 (Low), and the vector (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N) is internally consistent with the description: network-reachable but requiring high attack complexity (characteristic of the timing/observable-discrepancy side channel in CWE-203), user interaction (victim must load a crafted page), no privileges, unchanged scope, and only low confidentiality impact with no integrity or availability effect. All exploitation signals agree on low urgency: CISA SSVC reports Exploitation=none, Automatable=no, and Technical Impact=partial, which matches the single-origin, low-confidentiality leak. There is no CISA KEV listing and no public exploit identified, so there is no evidence of active exploitation. EPSS is not provided in the input and cannot be factored in. The one minor caveat is the AC:H designation - observable-discrepancy leaks often require favorable timing conditions and many repeated observations to extract meaningful cross-origin data, so real-world data exfiltration is slow and situational rather than a clean read. Overall this is a defense-in-depth patch, not an emergency. |
| Exploit ScenarioDerived | An attacker lures a victim into visiting a malicious web page that embeds cross-origin content and uses crafted CSS/Web Animations to measure an observable discrepancy (e.g., timing or rendering side effects) and infer cross-origin data the page should not be able to read. Because UI:R and AC:H apply, the victim must actively load the attacker's page and the attack depends on favorable conditions and repeated measurement. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Cross-origin information disclosure in Google Chrome prior to 155.0.8059.39 lets a remote attacker leak a limited amount of data from other origins when a victim loads a crafted HTML page that abuses an observable rendering discrepancy in Chrome's Animation implementation. Exploitation requires user interaction (the victim must open the attacker's page) and is rated high complexity (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N, CVSS 3.1), reflecting repeated timing/rendering measurement rather than a straightforward one-shot extraction; there is no code execution, data modification, or denial of service, and no public exploit identified at time of analysis. CISA's SSVC assessment rates exploitation as 'none' and automation as 'no', and no KEV listing applies, so this is a low-priority, low-real-risk issue despite affecting a ubiquitous browser.
RemediationAI
Vendor-released patch: Chrome 155.0.8059.39. Update Google Chrome to 155.0.8059.39 or later through the stable channel - the release announcement at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html documents this build as containing the fix for the Animation observable-discrepancy issue tracked at https://issues.chromium.org/issues/517429254 - and verify the installed version via chrome://version, noting that restarting the browser is required for the update to take effect. Because this is a renderer-side information-leak class bug rather than memory corruption, there is no meaningful standalone workaround: keeping Chrome's default Site Isolation enabled limits the blast radius but does not eliminate the side channel, disabling JavaScript outright would block the attack but is operationally impractical for most users, and blocking untrusted HTML content or restricting browsing to trusted origins is the only effective compensating control, at the cost of severely limiting web functionality. Given the high attack complexity, the requirement for victim interaction, and the limited confidentiality impact, patching on the normal update cadence is proportionate; organizations that cannot immediately update should prioritize the upgrade for high-risk browsing profiles rather than applying disruptive feature-disabling mitigations.
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 root cause is CWE-203 (Observable Discrepancy): Chrome's Animation subsystem produces a measurable difference in timing or rendering behavior that depends on cross-origin content the page should not be able to observe. This is a browser side-channel class of bug, where JavaScript running in an attacker-controlled page uses high-resolution timing and rendering state as a proxy to infer properties of cross-origin resources - a technique in the same family as CSS/rendering-based XS-Leaks and timing side channels. Because the discrepancy is inherent to how animations are scheduled and rendered (rather than a memory-safety fault), the disclosure is bounded to limited cross-origin information (C:L) and requires an unusually favorable, repeatable measurement setup, which is why the CVSS vector carries AC:H and UI:R while privilege requirements are none (PR:N). The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* identifies the Google Chrome browser as the affected component, and the fix lands in the Chromium Animation code as tracked in Chromium issue 517429254.
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:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Remote crafted page (AV:N) with no privileges (PR:N) but victim must load it (UI:R); side-channel timing makes it AC:H, and only a limited cross-origin read occurs (C:L, I:N, A:N).
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Observable discrepancy in Animation in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially obtain 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.
EUVD-2026-93725
GHSA-wwj7-wqgj-6mjr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB