Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious web page
-
ExploitServe crafted HTML exercising ANGLE
-
ExecutionTrigger improper input validation flaw
-
ImpactExecute arbitrary code within renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires the victim to be running Google Chrome prior to 156.0.8078.47 on Windows and to actively navigate to an attacker-controlled or compromised web page containing crafted HTML that exercises the ANGLE component (UI:R user interaction is mandatory). No authentication or prior privileges are needed (PR:N). The key limiting factor is that the resulting arbitrary code execution is confined to the renderer sandbox (S:U, 'inside the sandbox' per the description) - achieving host compromise would require chaining an additional sandbox-escape vulnerability. Exploitation is also constrained to the Windows build of Chrome as stated. |
| Impact | CVSS 3.1 base score is 8.8 (High) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, indicating a network-reachable, low-complexity, unauthenticated flaw that requires user interaction (visiting a crafted page) and yields high confidentiality, integrity, and availability impact. A critical nuance: scope is Unchanged (S:U) and the description explicitly states code execution occurs 'inside the sandbox' - this is renderer-level code execution, NOT a confirmed sandbox escape or full host compromise, which materially lowers real-world impact versus a standalone 8.8 reading. No EPSS score, SSVC decision data, or POC indicator was provided, and the CVE is not listed in CISA KEV, so exploitation probability cannot be quantified from the input; no public exploit identified at time of analysis. Google rated the underlying Chromium issue 'High' (not Critical), consistent with a sandboxed-RCE primitive that typically needs a chained sandbox-escape bug to be fully weaponized. Net assessment: this is a legitimate patch-now browser vulnerability given Chrome's ubiquity and the Chromium issue tracker reference, but there is no evidence of active or imminent widespread exploitation, so it should be prioritized via normal rapid-browser-patch cadence rather than emergency incident response. Missing data: EPSS and SSVC are absent - do not infer exploitation likelihood. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted content that exercises Chrome's ANGLE graphics component; when a victim on Windows (Chrome prior to 156.0.8078.47) visits it, improper input validation in ANGLE is triggered, allowing arbitrary code execution within the renderer sandbox. No authentication is required (PR:N) but the victim must actively load the malicious page (UI:R). No public exploit code was identified in the provided data, and full system compromise would additionally require chaining a separate sandbox-escape vulnerability. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Arbitrary code execution inside Chrome's renderer sandbox is possible in Google Chrome on Windows before 156.0.8078.47 through crafted HTML that triggers improper input validation in ANGLE. The attack is network-reachable, unauthenticated, and low-complexity but requires the victim to visit a malicious or compromised page; CVSS 3.1 is 8.8 (High), and successful exploitation is limited to code execution within the sandbox rather than direct host compromise. A vendor patch is available in 156.0.8078.47, and no public exploit or CISA KEV entry was identified at time of analysis.
RemediationAI
Upgrade Google Chrome on Windows to version 156.0.8078.47 or later via the Chrome stable-channel update and restart the browser so the new build is active; enterprise administrators should push this version through their update management tooling and verify the installed version across managed endpoints. The vendor advisory is https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and the Chromium issue is https://issues.chromium.org/issues/564064199. If immediate updating is not possible, reduce exposure by disabling WebGL or hardware acceleration on high-risk endpoints where operationally feasible, recognizing that this breaks many graphics-heavy web applications and is only a temporary risk reduction rather than a fix; because exploitation requires a user to visit a crafted page, restricting browsing to trusted sites and enforcing prompt restart after updates also lowers the window of exposure.
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
ANGLE is the graphics abstraction layer used by Chrome to translate OpenGL ES and WebGL workloads into platform graphics APIs, including Direct3D on Windows. CVE-2026-113334 is classified as CWE-20 improper input validation, meaning malformed or unexpected input reaching ANGLE is not adequately validated before use, allowing a crafted HTML page to influence graphics-processing behavior in a way that can lead to code execution inside the Chrome sandbox. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H confirms a network-reachable, low-complexity, unauthenticated issue that requires user interaction and has high confidentiality, integrity, and availability impact within the assessed scope; the independent assessment notes the execution is confined to the renderer sandbox, so full host compromise would require a separate sandbox-escape chain. No CPE strings were supplied, but EUVD identifies Chrome versions below 156.0.8078.47, and the vendor description limits the affected platform to Windows.
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:H/I:H/A:H
Remote crafted page with no auth (AV:N/PR:N) but mandatory page visit (UI:R); scope unchanged since code runs inside the sandbox (S:U), with high C/I/A within the renderer.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Improper input validation in ANGLE in Google Chrome on on Windows prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome on Windows is affected by a high-severity arbitrary code execution flaw in ANGLE that can be triggered when a user visits crafted HTML, with impact limited to Chrome's renderer sandbox rather than direct host compromise. Leadership should care because Chrome is broadly deployed, but exploitation requires user interaction and no public exploit was identified at time of analysis. The vendor-released patch is 156.0.8078.47.
Apply vendor patch.
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
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-105450
GHSA-gxvr-x833-mm8v
NVD
CVE.org
EPSS
Exploit-DB