EUVD-2026-111443
GHSA-p289-x7cf-jfw4
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage delivers malformed Skia graphics content
-
ExecutionTrigger memory corruption in Skia
-
ImpactExecute arbitrary code in renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
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 load attacker-controlled content in Google Chrome prior to 156.0.8078.73 - the CVSS UI:R metric and the 'crafted HTML page' wording mean a user must actively visit a malicious or compromised page, so this cannot be triggered without user interaction. No authentication is required (PR:N) and it is remotely reachable over the network (AV:N) against default configurations; no special Chrome feature or non-default setting is named as a prerequisite. The primary limiting factor is that code execution is confined to the renderer sandbox (S:U) - the description does not grant host-level compromise, so a separate sandbox-escape vulnerability would be needed to break out. The specific trigger mechanism within Skia is not described in the available sources beyond 'memory corruption' (CWE-119). |
| Impact | This is a genuine patch-priority issue but not a drop-everything emergency, consistent with the input's 'this_week' decision label. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) describes a network-reachable, low-complexity, unauthenticated flaw whose only gating factor is user interaction (the victim must load a crafted HTML page). Crucially, the description states code execution occurs 'inside the sandbox' with scope unchanged (S:U) - this is renderer-level compromise, not a full sandbox escape, so an attacker would still need a separate escape bug to reach the host. Google rates the Chromium severity 'High'. No EPSS score, no CISA KEV listing, and no verified public exploit were supplied, so there is no evidence of active exploitation; the two chromium.googlesource/issues.chromium.org references are a vendor bug-tracker entry and a release note, not working exploit code. The signals are therefore internally consistent: a serious, broadly-reachable browser RCE primitive, patched, but with no current exploitation evidence and a required user-interaction step that tempers real-world urgency. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malformed graphics content that triggers the Skia memory-corruption flaw, then lures a victim running an unpatched Chrome (before 156.0.8078.73) to visit it. When the page renders, the attacker achieves arbitrary code execution within the browser's sandboxed renderer process. No public exploit code was identified in the provided data, and full system compromise would additionally require a separate sandbox-escape vulnerability. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Memory corruption in the Skia graphics library shipped in Google Chrome before 156.0.8078.73 allows a remote attacker to achieve code execution inside the renderer sandbox when a victim loads a crafted HTML page. Affected users are those running Chrome builds prior to 156.0.8078.73; exploitation requires user interaction (CVSS UI:R, PR:N, AV:N), and the impact is confined to the renderer sandbox rather than host-level compromise. No public exploit is identified at time of analysis, and EPSS/KEV signals were not provided; the vendor classifies the issue as Chromium security severity High.
RemediationAI
Vendor-released patch: Chrome 156.0.8078.73. Update Google Chrome to 156.0.8078.73 or later through the browser's built-in updater or your distribution's package channel, and verify the installed version after restarting the browser so that pending updates complete; enterprise fleets should push the fixed build via their Chrome management tooling. The advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html documents the release, and the underlying bug is tracked at https://issues.chromium.org/issues/570825067. No workarounds or compensating controls are described in the available sources; the impact of this issue is bounded by the renderer sandbox, so a separate sandbox-escape flaw would be required for host-level compromise.
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
Skia is Chrome's 2D graphics engine and a large native C++ attack surface that parses and renders attacker-supplied web content, so memory-safety defects there are reachable from ordinary page rendering. The flaw is classified CWE-119 (improper restriction of operations within the bounds of a memory buffer), and the vendor describes it as memory corruption. The specific trigger within Skia is not described in the available sources. Per the assessed vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), an unauthenticated remote attacker must persuade a victim to load crafted HTML, after which corruption of memory can be turned into arbitrary code execution at the privilege level of the Chrome renderer; the scope metric is Unchanged, so privileges gained are bounded by the renderer sandbox and a separate sandbox escape would be required for host compromise.
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:U/C:H/I:H/A:H
Remote crafted page needs no auth (AV:N/PR:N) but requires the victim to visit it (UI:R); execution stays in the renderer sandbox (S:U) with full C/I/A impact there.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in Skia in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 1
Executive ViewAI
A high-severity memory corruption flaw in Google Chrome's Skia graphics library (CVE-2026-118351) could allow a remote attacker to execute code within the browser's renderer sandbox when a user visits a malicious webpage. Until Chrome is updated to version 156.0.8078.73, employees remain exposed, and although the impact is confined to the sandbox, a compromised renderer could serve as a foothold for further attacks. Leadership should prioritize patching to maintain endpoint integrity and reduce risk to the organization's data and operations.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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