EUVD-2026-34441
GHSA-q9j8-hmj6-qjhp
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Insufficient data validation in Animation in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Memory disclosure in Google Chrome's Animation component (all versions prior to 149.0.7827.53) enables an unauthenticated remote attacker to read potentially sensitive data from the browser's process memory by directing a victim to a crafted HTML page. The flaw arises from insufficient data validation during animation processing - a class of bug that typically permits out-of-bounds or uninitialized memory reads rather than code execution. No public exploit code has been identified at time of analysis, and the EPSS score of 0.03% (11th percentile) confirms low current exploitation probability despite the CVSS confidentiality impact being rated High.
Technical ContextAI
The vulnerability resides in Chrome's Animation subsystem, the rendering engine component responsible for processing CSS Animations and the Web Animations API. Insufficient data validation in this layer likely permits reads beyond allocated buffer boundaries or access to uninitialized memory during animation frame evaluation triggered by crafted HTML. The affected product is precisely identified by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome desktop versions prior to the stable channel release 149.0.7827.53. No CWE was formally assigned, but the 'insufficient data validation' root cause description combined with the Information Disclosure tag points to an improper input validation or out-of-bounds read class of defect. Google's internal Chromium severity rating of Medium is consistent with a memory-read primitive that lacks a code execution component.
RemediationAI
The primary fix is to update Google Chrome to version 149.0.7827.53 or later, delivered via Chrome's built-in silent updater or obtainable through the stable channel release documented at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Enterprise administrators managing Chrome via Group Policy or endpoint management platforms (Intune, Jamf, etc.) should push this update immediately. Where patching cannot be deployed immediately, compensating controls include enforcing URL allowlists or web proxy filtering to prevent user access to untrusted or unknown web content - this reduces exposure but degrades browsing flexibility. Browser isolation solutions (e.g., remote browser isolation) would fully neutralize the attack vector by preventing malicious page content from executing in a local process, though at significant infrastructure cost. Disabling JavaScript enterprise-wide would prevent exploitation but is not operationally viable in most environments. The patch is confirmed available per the vendor advisory; no workaround eliminates the underlying flaw.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today