EUVD-2026-105522
GHSA-j9g8-w56c-vcv3
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted web page
-
DeliveryDeliver malicious HTML content
-
ExploitTrigger memory corruption in CredentialProvider
-
ExecutionEscape Chrome browser sandbox
-
ImpactExecute arbitrary code on Windows host
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 a Windows user running Chrome prior to 156.0.8078.47 to actively navigate to an attacker-controlled crafted HTML page (UI:R), which triggers memory corruption in the CredentialProvider component and a sandbox escape. The limiting factor is the mandatory user interaction - the victim must be lured into loading the malicious content; there is no evidence of drive-by exploitation without navigation. No authentication is required (PR:N). Exploitation is further constrained to the Windows platform and to unpatched versions below 156.0.8078.47; updated Chrome builds are not affected. |
| Impact | Signals conflict sharply and must be reconciled before prioritization. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) yields a 9.6 Critical score driven by network reach, low complexity, no privileges, a scope change (sandbox escape), and full CIA impact - yet Google's own Chromium severity rating for this issue is only Medium. This divergence suggests the 9.6 is a formula-maximal score (scope change plus triple-H impact) rather than an indicator of easy mass exploitation; the one mitigating factor, UI:R, means a user must be lured to a crafted page. No EPSS probability was supplied, the vulnerability is NOT in CISA KEV, and no public POC is referenced, so there is no evidence of active or imminent exploitation. On balance this is a 'patch-promptly' browser RCE/sandbox-escape, not a drop-everything emergency: the headline 9.6 overstates real-world risk relative to the vendor's Medium rating and the absence of exploitation signals. Verify the severity discrepancy against the Chrome release advisory, as the vendor rating and NVD/base score materially disagree. |
| Exploit ScenarioDerived | An attacker hosts a crafted HTML page and lures a Windows Chrome user to visit it (e.g., via phishing or a malvertising redirect). Rendering the page triggers memory corruption in the CredentialProvider component, enabling the attacker to escape the renderer sandbox and run arbitrary code on the host. No public exploit code is identified at time of analysis, so weaponization would require independent development. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Sandbox escape in Google Chrome on Windows (versions prior to 156.0.8078.47) lets a remote attacker who lures a victim to a crafted HTML page trigger memory corruption in the CredentialProvider component and potentially execute code outside the Chrome sandbox. The attack is unauthenticated (PR:N) but requires user interaction (UI:R) - the victim must navigate to attacker-controlled content - and is confined to the Windows platform on unpatched builds. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, though the vendor rates the underlying bug only 'Medium' (Chromium security severity) while the CVSS 3.1 vector scores 9.6 with a scope change (S:C), a discrepancy that reflects Google's typical treatment of sandbox-escape primitives that must be chained with a separate renderer compromise to achieve full code execution.
RemediationAI
Vendor-released patch: upgrade Google Chrome on Windows to 156.0.8078.47 or later (Stable channel update published at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html); confirm the installed build via chrome://version and, for fleets, via Chrome Enterprise / your browser management console, forcing an update check if the auto-updater has not yet staged the release. Because the defect sits in the CredentialProvider broker component and is reachable from ordinary web content, no reliable configuration-level workaround exists - disabling individual web platform features does not remove the exposed code path, and blocking the CredentialProvider integration may impair Windows credential/passkey sign-in flows without guaranteeing immunity. Compensating controls until patching completes: restrict affected hosts to an allowlisted set of trusted sites via enterprise URL blocklisting (reduces, but does not eliminate, exposure to crafted pages and costs user flexibility), run Chrome in a hardened/isolated environment or on dedicated low-privilege accounts so a sandbox escape yields limited host access, and prioritise the update on endpoints where the browser runs alongside stored credentials. Note that the Chromium issue tracker entry (https://issues.chromium.org/issues/502085234) may remain access-restricted, so the release notes are the authoritative fix reference.
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 flaw is a CWE-119 improper-restriction-of-operations-within-a-memory-buffer (memory corruption) defect in Chrome's CredentialProvider on Windows - the component that brokers Chrome's integration with the Windows credential/authentication subsystem rather than the renderer's HTML parsing paths. Because the corruption is reachable from a crafted HTML page (AV:N) yet manifests in a browser-process/broker component, the CVSS vector assigns S:C (scope change) and C:H/I:H/A:H, i.e. successful exploitation crosses the Chrome sandbox boundary and compromises the host user context rather than only the renderer. In practice such a primitive is a sandbox-escape stage: an attacker would normally pair it with a renderer-side memory-corruption bug to go from a web page to host code execution, which is consistent with the modest 'Medium' Chromium severity rating despite the high CVSS base score. The high attack complexity penalty is absent (AC:L) but the vector's UI:R reflects the mandatory navigation/luring step; no CPE identifiers were supplied in the source data, so affected scope is taken from the vendor advisory and EUVD (Chrome on Windows below 156.0.8078.47).
Know when Windows 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 delivery gives AV:N/AC:L/PR:N, user navigation forces UI:R, and code execution outside the sandbox is a scope change (S:C) with full host compromise (C/I/A:H).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in CredentialProvider in Google Chrome on on Windows prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Articles & Coverage 1
Executive ViewAI
Google Chrome on Windows builds prior to 156.0.8078.47 carries a critical sandbox-escape flaw in the CredentialProvider component that, if successfully chained with a separate browser-renderer compromise, could let an attacker break out of Chrome's security boundary and run code on the endpoint. Because Chrome is widely deployed across the Windows workforce and the attack only requires a user to visit attacker-controlled content, leadership should treat fleet-wide browser currency as a near-term priority even though no public exploit or active exploitation has been identified.
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.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
Exploit-DB