EUVD-2026-105532
GHSA-g9x8-vf5c-7qmv
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryMalicious CSS parsed by renderer
-
ExploitTrigger memory corruption in CSS engine
-
ExecutionRead adjacent sandbox memory
-
ImpactExfiltrate leaked data/pointers
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 open a crafted HTML page containing malicious CSS that triggers the memory-corruption condition in Chrome's CSS engine (UI:R active user navigation). No authentication or elevated privileges are needed (PR:N), and default Chrome configurations are affected since no special feature toggle is cited. Limiting factors: the read is bounded to memory inside the renderer sandbox (no sandbox escape, no code execution, no data modification per I:N/A:N), and users running Chrome 156.0.8078.47 or later are not affected. The user-interaction requirement means drive-by or social-engineering delivery is necessary - the flaw cannot be triggered against a browser that never visits attacker-controlled content. |
| Impact | This is a moderate-risk browser flaw that does not warrant emergency prioritization. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, base 6.5) describes network-reachable, low-complexity, unauthenticated exploitation that nonetheless requires user interaction (visiting a crafted HTML page), with a confidentiality-only impact - consistent with the description's 'potentially read memory inside the sandbox.' Multiple independent signals point to low real-world urgency: EPSS is 0.18% (8th percentile), the vulnerability is NOT on CISA KEV, and no public proof-of-concept is referenced. Chromium itself rated the severity only Medium. One point of tension worth noting: the CVSS vector lists C:H (total confidentiality loss), yet the description constrains the read to memory 'inside the sandbox' and uses the hedging word 'potentially,' which argues for a more limited confidentiality impact than C:H implies - my independent assessment downgrades this. Net: a legitimate memory-safety bug to patch on normal cadence, not a high-real-risk issue despite the network attack vector. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted CSS that triggers the memory-corruption condition in Chrome's CSS handling, then lures a victim into visiting it. On rendering, the flaw lets the attacker potentially read memory contents within the renderer sandbox, possibly leaking sensitive data or defeating memory-layout mitigations. No public exploit code is identified at time of analysis, and exploitation requires the victim to actively load the malicious page. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption within Chrome's CSS engine lets a remote attacker read memory that is otherwise confined to the renderer sandbox by convincing a user to open a crafted HTML page in any Chrome build prior to 156.0.8078.47. The CVSS vector (AV:N/AC:L/PR:N/UI:R) means no credentials are needed, but the attack is not drive-by-silent: it depends on the victim navigating to attacker-controlled content, so it is a social-engineering or malicious-page delivery problem rather than a wormable one. Impact is bounded to information disclosure inside the sandbox - there is no sandbox escape, no code execution and no data modification - and our independent assessment rates confidentiality impact as Low rather than the vendor-published High, giving a moderate-risk browser flaw that does not warrant emergency prioritization. EPSS is just 0.18% (8th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis, though Google has shipped a fix in 156.0.8078.47.
RemediationAI
Upgrade Google Chrome to 156.0.8078.47 or later - the vendor-released patch for this issue - via the built-in updater or a fresh install from the official channel, and confirm the reported version in chrome://version; the release notes are at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and the technical detail is in https://issues.chromium.org/issues/504107363. Because exploitation requires the user to open a crafted page, interim compensating controls are practical: enforce enterprise policy to block untrusted or uncategorized sites and aggressive ad/third-party content filtering, which reduces exposure to malicious stylesheets at the cost of some legitimate site breakage, and enable site isolation (on by default, but verify it has not been disabled) so any leaked renderer memory stays origin-confined. There is no configuration toggle that disables the vulnerable CSS parsing path, so patching is the only complete fix; restart the browser after updating since Chromium applies updates on relaunch. Downstream Chromium-based browsers (Edge, Brave, Opera, Electron applications) should follow their own vendor advisories for equivalent builds.
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 defect is a CWE-119 improper-restriction-of-operations-within-a-memory-buffer condition in the CSS parsing/layout component of the Chromium renderer. Chrome's multi-process architecture means CSS is handled in a heavily sandboxed renderer process, so a successful out-of-bounds read yields memory contents from that process only - it cannot by itself be pivoted into a sandbox escape or arbitrary code execution from the browser's perspective. Triggering requires the renderer to process a maliciously shaped stylesheet embedded in an HTML page, which means the victim must actually load the page (UI:R); no authentication or elevated privileges are involved (PR:N) and default configurations are exposed because no special flag or feature toggle is implicated. Google rates the flaw Medium under its Chromium security severity scale, reported internally via chrome-cve-admin@google.com and tracked in Chromium issue 504107363; ENISA EUVD cross-references it as EUVD-2026-105532. The realistic threat is speculative leakage of renderer-resident data (potentially including same-origin secrets held in that process), which is meaningful but well short of full compromise given I:N/A:N.
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:N/A:N
Network-reachable via web page (AV:N) with no auth (PR:N) but mandatory user navigation (UI:R); impact is a bounded, sandbox-limited memory read ('potentially'), so C:L rather than C:H, with I:N/A:N.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Memory corruption in CSS in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
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.
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