Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryLoad malicious animation content
-
ExploitTrigger missing authorization in Animation
-
ExecutionBypass web origin policy
-
ImpactManipulate cross-origin resource
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to actively load an attacker-controlled HTML page in Chrome (UI:R / user interaction), which is the primary limiting factor - there is no fully passive, zero-interaction path. No authentication to any service is required (PR:N), and default Chrome configurations prior to 155.0.8059.39 are affected, so no special feature flag or non-default setting is needed. Exploitation is bounded to Chrome browser instances on the vulnerable version range and does not affect server-side components. The practical limiter is therefore social-engineering success in getting a user to visit the malicious page plus the browser remaining unpatched. |
| Impact | This is a genuine but moderate-priority issue, not a top-tier emergency. The vendor CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N, 6.5 Medium) indicates a network-reachable flaw that an unauthenticated attacker can trigger with low complexity but ONLY if the victim is lured to a crafted HTML page (UI:R). Impact is confined to integrity (I:H) via a same/web-origin policy bypass in Chrome's Animation component - no direct confidentiality (C:N) or availability (A:N) impact is claimed by Google, consistent with its own 'Medium' Chromium severity rating. All exploitation signals point AWAY from urgency: EPSS is only 0.20% (9th percentile), there is no CISA KEV listing, and no public POC was identified, so this is 'no public exploit identified at time of analysis.' No SSVC decision record was provided. One point worth verifying: a 'web origin policy bypass' typically enables cross-origin data theft, which would normally imply a confidentiality impact, yet the vector rates C:N and I:H - this C/I split should be confirmed against Google's advisory, as the real-world effect (e.g., leaking or manipulating cross-origin content) may be broader than a pure integrity label suggests. Overall: patch in the normal browser-update cycle; it does not warrant out-of-band emergency response absent exploitation evidence. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page and lures a Chrome user (via phishing link, malvertising, or compromised site) to visit it. The crafted page abuses a missing authorization check in the Animation component to bypass the web origin policy, allowing the attacker's origin to influence or access resources it should not. No public exploit code was identified, and successful attack requires the victim to open the page. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Missing authorization in Chrome's Animation component (CWE-862) affects Google Chrome versions prior to 155.0.8059.39 and lets a remote, unauthenticated attacker bypass web origin policy when a victim loads a crafted HTML page. The attack is not passive: exploitation requires the user to navigate to attacker-controlled content (UI:R), but no credentials or non-default browser settings are needed, and success is bounded to an integrity impact (C:N/I:H/A:N) on the browser session rather than code execution or data theft. No public exploit code was identified and there is no confirmed active exploitation (no CISA KEV listing); EPSS is 0.20% (9th percentile), and a vendor patch is available, making this a moderate-priority, patch-and-move-on issue.
RemediationAI
Vendor-released patch: upgrade Google Chrome to version 155.0.8059.39 or later via chrome://settings/help or the Chrome stable channel advisory (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html), and confirm the version in chrome://version afterwards; for managed fleets, force the update through enterprise policy rather than relying on user-initiated updates, since the vulnerability persists for as long as the browser stays on an older build. There is no configuration toggle that removes the vulnerable Animation path, so the meaningful compensating controls are behavioral: block or heavily filter untrusted/anonymous web content for high-risk user groups, and enforce network-layer controls (secure web gateway, DNS/proxy blocklists) plus user awareness for the social-engineering step the attack depends on. These workarounds carry real trade-offs - content filtering degrades user productivity and can break legitimate sites, and it does not eliminate the flaw on devices that must reach the open internet, so they should be treated strictly as stopgaps until patching is complete. Because exploitation requires the victim to load the crafted page (UI:R), reducing casual browsing of untrusted links is the only layered mitigation with any traction, but it is weaker than patching and should not be relied on alone.
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 affected code is the Animation subsystem of the Chromium rendering engine that ships in Google Chrome (CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, i.e. all builds below 155.0.8059.39). The root cause class is CWE-862 Missing Authorization: an animation-related code path fails to perform the required authorization/origin check, so an attacker-supplied web page can act outside the origin boundary that the browser is supposed to enforce. The published CVSS:3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N describes a network-delivered, low-complexity attack requiring victim interaction, with scope unchanged and high integrity impact but no confidentiality or availability impact - consistent with a same-origin/authorization enforcement failure that lets crafted content influence state it should not be able to reach, rather than a memory-corruption or RCE primitive. The impact is confined to client-side Chrome instances; no server-side component is involved, so the practical constraint is social-engineering the victim into rendering the malicious page on an unpatched browser.
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:N/I:H/A:N
Remotely reachable via a crafted page with no auth (AV:N/PR:N) but requires the victim to visit it (UI:R); impact is an integrity-affecting origin bypass (I:H) with no claimed confidentiality or availability effect.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Missing authorization in Animation in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to bypass web origin policy 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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-93861
GHSA-4rfr-vf62-3h6x
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB