EUVD-2026-91707
GHSA-7q6f-h37m-rrqf
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted page
-
DeliveryDeliver malicious HTML to Chrome
-
ExploitTrigger FileSystem authorization flaw
-
ExecutionEscape renderer sandbox
-
ImpactExecute arbitrary code on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the victim to be running Google Chrome on Windows at a version prior to 154.0.8037.97, and to be socially engineered into opening an attacker-controlled crafted HTML page (UI:R) - exploitation is not automatic or zero-click. The flaw resides in the FileSystem component's authorization checks; no special non-default Chrome configuration is indicated as required. Limiting factors: mandatory user interaction (victim must visit the page), platform restriction to Windows (other OSes not listed as affected), and the version ceiling, which auto-update to 154.0.8037.97 or later fully remediates. |
| Impact | Signals are mixed and should be weighed carefully. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6 Critical) describes a network-reachable, low-complexity, unauthenticated sandbox escape with scope change and full confidentiality/integrity/availability impact - a severe technical outcome confirmed by SSVC Technical Impact: total. However, SSVC Exploitation is rated 'none' and Automatable is 'no', and the EPSS score is only 0.21% (10th percentile), indicating no observed exploitation and low near-term probability. This is not in CISA KEV and no POC is referenced, so exploitation status is 'no public exploit identified at time of analysis.' The UI:R requirement plus the description's explicit reliance on social engineering (luring a victim to a crafted page) materially lowers real-world risk versus a drive-by RCE - Automatable:no aligns with this, as each victim must be individually enticed. Net assessment: a genuinely high-impact bug that warrants prompt patching given Chrome's ubiquity, but current intelligence points to targeted/opportunistic rather than mass exploitation; EPSS and SSVC both argue against emergency escalation beyond normal fast-track browser patching. Note the CWE-863 (incorrect authorization) classification is a logic/authorization flaw rather than a classic memory-corruption bug, which is consistent with the 'FileSystem incorrect authorization' description. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page and uses social engineering (phishing link, malicious ad, or compromised site) to convince a Windows Chrome user to open it. The page abuses the FileSystem component's incorrect authorization to break out of the renderer sandbox and execute arbitrary code on the host. No public exploit code is identified at time of analysis, and the attack requires user interaction (visiting the page), so it is not a zero-click drive-by. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 03, 2026
Sandbox escape and arbitrary code execution in Google Chrome on Windows (versions prior to 154.0.8037.97) arise from incorrect authorization in the browser's FileSystem component, letting a remote, unauthenticated attacker break out of the renderer sandbox and run code at the browser's privilege level after convincing a victim to open a crafted HTML page. Exploitation requires the user to visit an attacker-controlled page (CVSS PR:N/UI:R, scope changed) and is neither automatic nor zero-click; no public exploit identified at time of analysis, and CISA's SSVC rates exploitation as none with automatable flagged no. That said, the signal is mixed: 9.6 CVSS with total technical impact contrasts with a low EPSS of 0.21% (10th percentile) and a platform-restricted, interaction-dependent attack path.
RemediationAI
Vendor-released patch: Chrome 154.0.8037.97 (or later) for Windows - upgrade immediately via Chrome's built-in update (chrome://help / relaunch browser) or by deploying the current stable Enterprise MSI, then verify the installed build in chrome://version and with a patch-management scan. Google's stable-channel advisory (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop.html) documents the fixed release, and the Chromium issue https://issues.chromium.org/issues/553114097 provides the underlying report; auto-update to 154.0.8037.97 or later fully remediates, since the flaw is a version-ceiling issue rather than a configuration defect. Google has not published a documented workaround, so interim risk reduction must come from compensating controls with real trade-offs: apply the FileSystemReadBlockedForUrls and FileSystemWriteBlockedForUrls enterprise policies to deny the File System Access API permission on untrusted internet zones, accepting that legitimate browser-based editors and local-file web apps will break for those sites; constrain users to managed, updated browsers and block untrusted/uncategorized sites at the proxy or DNS layer, which reduces exposure to the socially engineered lures the attack depends on but does not eliminate it; and reinforce phishing/user-awareness training since successful exploitation requires the victim to open a crafted HTML page (UI:R), meaning user interaction - not authentication - is the gating precondition.
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-863 (Incorrect Authorization) inside Chrome's FileSystem component - the code path that mediates the File System Access API's permission model between an untrusted renderer and Chrome's privileged/sandboxed file-handling service. Chrome's security architecture assumes the renderer is untrusted and relies on broker-side authorization checks before any privileged file operation is granted to a web origin; a missing or incorrect check of that authorization decision means a malicious page can satisfy the renderer-side logic without the broker enforcing the corresponding per-origin permission, breaking the sandbox boundary. The CVSS scope change (S:C) and C:H/I:H/A:H reflect exactly that boundary crossing - the flaw's impact is measured on Chrome rather than on the sandboxed renderer, matching CISA's SSVC 'total' technical impact rating. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* with a fixed version ceiling of 154.0.8037.97, and the reporter/patch channel is Google's own Chrome stable release; the description scopes the flaw to Windows builds, so the FileSystem implementation or its O/S folder-permission handling specific to Windows is implicated, and other platforms are not listed as affected.
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
Crafted web page gives AV:N/AC:L/PR:N; social engineering to open the page is UI:R; sandbox escape to the host is S:C with full C/I/A impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Incorrect authorization in FileSystem in Google Chrome on on Windows prior to 154.0.8037.97 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome on Windows versions prior to 154.0.8037.97 are affected by a critical sandbox escape vulnerability that allows a remote unauthenticated attacker to execute arbitrary code at the browser's privilege level, though user interaction is required to visit a malicious page. Although no public exploit has been identified and the exploit probability is currently low, the potential for full system compromise poses a significant risk to organizational assets and data. Leadership should prioritize patching to mitigate this high-severity threat and protect against potential unauthorized access.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
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
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
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
Exploit-DB