EUVD-2026-111464
GHSA-jm9j-h2jw-qpc5
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryPage delivers malicious SVG content
-
ExploitTrigger use-after-free in SVG handling
-
ExecutionExecute code outside Chrome sandbox
-
ImpactFull host compromise under user privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, 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 open an attacker-controlled crafted HTML page that embeds malicious SVG content in Google Chrome prior to 156.0.8078.73 (UI:R) - no authentication, no privileges, and no special configuration are needed, as the flaw affects default SVG rendering. The primary limiting factor is the required user interaction (the victim must navigate to the page); the primary aggravating factor is that successful exploitation escapes the Chrome sandbox, elevating impact from a contained renderer compromise to arbitrary code execution on the host under the browser user's privileges. Updating to 156.0.8078.73 or later is the vendor-provided fix. |
| Impact | This is a genuine high priority, not an inflated CVSS number. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6) describes a network-reachable, low-complexity, unauthenticated memory-corruption flaw whose scope-changed (S:C) rating reflects the critical detail in the description: code execution OCCURS OUTSIDE THE CHROME SANDBOX, i.e. full host compromise rather than a contained renderer crash. The only brake is UI:R - a victim must open a crafted HTML page. The signals partly conflict on likelihood: EPSS is just 0.22% (13th percentile), yet the vuln.today decision label is act_now and the vendor (Google, via chrome-cve-admin@google.com) rates it High. The low EPSS is best read as 'no broad exploitation observed/predicted yet,' which is normal for a freshly patched Chrome bug, and should NOT override the act_now urgency driven by sandbox-escape impact and the browser's ubiquity. There is NO CISA KEV listing and NO confirmed public exploit in the input, so this is not confirmed active exploitation. Bottom line: patch now per the act_now label; the risk is real because of impact and reach, even though measured exploitation probability is currently low. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted SVG content and lures a victim to visit it (UI:R). Rendering the SVG triggers the use-after-free in Chrome's SVG handling, and because the flaw allows code execution outside the sandbox, the attacker can potentially run arbitrary code on the victim's host with the browser user's privileges. No public exploit identified at time of analysis; the linked Chromium issue (574791952) is a restricted bug-tracker entry, not a working PoC. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Use-after-free in Google Chrome's SVG handling lets a remote attacker who gets a victim to open a crafted HTML page run arbitrary code outside the browser sandbox, affecting Chrome builds prior to 156.0.8078.73. Exploitation needs no authentication or privileges (CVSS PR:N) and no special configuration, since it involves default SVG rendering; the only gate is the required user interaction of loading the page (UI:R), while the changed scope plus high confidentiality, integrity and availability impact give CVSS 9.6 / Chromium severity High. Google has published a fixed build in the stable channel and the priority assessment is act_now; EPSS is modest at 0.22% (13th percentile), the CVE is not in CISA KEV, and no public exploit has been identified at time of analysis.
RemediationAI
Vendor-released patch: 156.0.8078.73. Update Google Chrome to 156.0.8078.73 or later using the built-in updater (chrome://settings/help) and fully restart the browser, since a restart is required before the new binary replaces the vulnerable renderer. Enterprise and managed fleets should push the same version through their existing update or management tooling and verify reported client versions against 156.0.8078.73. Operators of Chromium-based or embedded browsers should track the corresponding upstream fix. The vendor advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html and the Chromium issue at https://issues.chromium.org/issues/574791952 are the authoritative references; the supplied sources present updating as the fix and do not list configuration-level workarounds, so no feature disablement or port restriction is documented here as a 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 root cause is CWE-416, use-after-free: an object is released while a reference to it remains, so later use of that dangling reference can corrupt memory and, in a browser engine, be steered into code execution. Here the affected subsystem is Chromium's SVG rendering in the Blink renderer, reached through ordinary HTML content that embeds SVG, so any page the user visits is a potential delivery vehicle. The advisory classifies the impact as code execution outside the sandbox, meaning the flaw is not expected to stay contained within the renderer process sandbox that normally limits a renderer compromise. The supplied sources do not describe the specific SVG element, animation or lifetime transition that triggers the free, so the precise trigger is not described in the available sources. Tags accompanying the record also flag denial of service and memory corruption, consistent with a dangling-pointer defect whose simplest outcome is a renderer crash.
Know when Chrome gets its next vulnerability
- 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:C/C:H/I:H/A:H
Remote crafted page, no privileges, low complexity; UI:R because the victim must load the page; S:C and C/I/A:H because execution escapes the sandbox to the host.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in SVG in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome versions prior to 156.0.8078.73 contain a critical use-after-free vulnerability (CVE-2026-118308) in SVG rendering that allows remote code execution outside the browser sandbox. This affects all employees using unpatched Chrome, exposing the organization to potential data breaches, system compromise, and operational disruption if a user visits a malicious webpage.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
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
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Exploit-DB