Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost crafted HTML page
-
DeliveryLure victim via social engineering
-
ExploitVictim opens page in vulnerable Chrome
-
ExecutionTrigger incorrect reference resolution in FileSystem
-
PersistEscape renderer sandbox
-
ImpactExecute arbitrary code on host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Incorrectly specified target
|
| Exploitation Conditions | Exploitation requires the victim to actively open or interact with an attacker-crafted HTML page (CVSS UI:R plus the description's explicit 'leveraging social engineering'), so it cannot be triggered fully unattended - the user must be lured to malicious content. The target must be running Chrome prior to 152.0.7977.65; no authentication or elevated privileges are needed on the target (PR:N). The key limiting factor is this required user interaction and the fact that the outcome is described as 'potential' code execution, indicating exploitation is not guaranteed; the sandbox-escape nature (S:C) is what makes success high-impact when it does occur. |
| Impact | Signals conflict and should be weighed carefully. The supplied CVSS 3.1 base score is 9.6 (Critical) driven by network vector, low complexity, no privileges, scope change (S:C, reflecting the sandbox escape) and high C/I/A impact - but the only limiting metric is UI:R (user interaction). Notably, Chromium's own security team rated the severity Medium, and EPSS is low at 0.45% (38th percentile), which argues against imminent mass exploitation. There is no CISA KEV listing and no public exploit identified, so this is not confirmed actively exploited. The realistic priority is moderate: a sandbox escape is serious, but it requires social engineering to land a victim on a malicious page, exploitation is described as only 'potential,' and the vendor's Medium rating plus low EPSS suggest the 9.6 overstates real-world urgency. Patch promptly as part of normal Chrome update cadence rather than treating it as an emergency. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page that abuses the incorrect reference resolution in Chrome's FileSystem code and uses social engineering (phishing link, malvertising, or a compromised site) to get a victim to open it in a vulnerable Chrome build. If successful, the page escapes the renderer sandbox and executes attacker-controlled code on the victim's machine. No public proof-of-concept has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Sandbox escape in Google Chrome's FileSystem component before version 152.0.7977.65 lets a remote attacker who lures a victim to a crafted HTML page potentially run arbitrary code outside the renderer sandbox. The flaw stems from incorrect reference resolution (CWE-706) and requires user interaction via social engineering. It is patched in the stable channel; there is no public exploit identified and EPSS exploitation probability is low (0.45%).
RemediationAI
Vendor-released patch: Google Chrome 152.0.7977.65 (Stable channel) - upgrade to that version or later immediately; Chrome typically auto-updates, so verify the running version via chrome://settings/help and relaunch to apply. Refer to Google's advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html for platform-specific builds. In managed environments, push the update through your browser management/GPO/MDM tooling and force a restart to complete installation. As an interim compensating control before patching, user-awareness measures against social-engineering lures (since exploitation requires the victim to open a crafted page) and web filtering to block untrusted sites reduce exposure, with the trade-off of limited coverage; there is no feature-level toggle to disable the affected FileSystem code without breaking legitimate site functionality, so patching is the definitive fix.
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 vulnerability lives in Chrome's FileSystem implementation, part of the Blink/Chromium renderer that brokers web-page access to sandboxed file storage. CWE-706 (Use of an Incorrectly-Resolved Name or Reference) means the component resolves a file or object reference to the wrong target, which in a sandbox-boundary context can allow the renderer process to reach resources or code paths it should not - the basis for a sandbox escape. The single affected CPE is cpe:2.3:a:google:chrome (all versions prior to the fix), covering the desktop Chrome browser built on the Chromium engine, so the same defect likely affects other Chromium-derived browsers until they merge the upstream fix.
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:C/C:H/I:H/A:H
Remote crafted page (AV:N) but exploitation is only 'potential' and needs social engineering plus a sandbox escape, so AC:H and UI:R; PR:N and S:C for the sandbox boundary crossed.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Incorrect reference resolution in FileSystem in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Executive ViewAI
Google Chrome's FileSystem component contains a critical vulnerability (CVE-2026-78985) that allows attackers to execute arbitrary code on affected devices when users visit malicious websites, potentially compromising sensitive business data and employee systems. The vulnerability affects all Chrome users across your organization until patched, exposing both internal resources and customer-facing operations. A vendor patch (version 152.0.7977.65) is available, and deployment should be prioritized despite currently low exploitation activity.
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.
Vendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-65853
GHSA-jwpm-4vmf-pv72
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB