Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-93695 Overview
CVE-2026-93695 affects Progress ShareFile Storage Zones Controller version 5.12.6 and below. The FileCopyService component uses a remote file identifier when constructing a local temporary file path without enforcing containment. Attackers can direct the service to write attacker-controlled content to arbitrary filesystem locations writable by the service account. When an executable Internet Information Services (IIS) directory is writable, this behavior enables remote code execution. The flaw is categorized as a path traversal weakness under [CWE-22].
Critical Impact
Attackers can achieve remote code execution on affected Storage Zones Controllers by writing attacker-controlled files into IIS-served directories through unsanitized remote file identifiers.
Affected Products
- Progress ShareFile Storage Zones Controller v5.12.6 and below
- FileCopyService component within the Storage Zones Controller
- IIS-hosted ShareFile storage endpoints running vulnerable controller versions
Discovery Timeline
- 2026-10-12 - CVE-2026-93695 published to the National Vulnerability Database (NVD)
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-93695
Vulnerability Analysis
The vulnerability resides in the FileCopyService of Progress ShareFile Storage Zones Controller. When processing file copy operations, the service builds a local temporary file path from a remote file identifier supplied in the request. The construction routine does not validate or canonicalize the resulting path against an expected base directory. Attackers can embed traversal sequences or absolute path components in the remote identifier. The service then writes attacker-controlled content outside the intended staging directory, into any location writable by the service account.
Successful exploitation requires local attack conditions and high attack complexity, but delivers high confidentiality, integrity, and availability impact. When writable directories overlap with IIS-served executable paths, the written content can be executed by the web server, resulting in remote code execution under the service account context.
Root Cause
The root cause is improper limitation of a pathname to a restricted directory [CWE-22]. The FileCopyService trusts the remote file identifier as a safe path fragment. It does not enforce containment within a designated temporary directory. No canonicalization, allowlist, or path normalization check is applied before the write operation. See the ShareFile Security Vulnerability Report for vendor technical details.
Attack Vector
The attack vector is local with high complexity and no authentication or user interaction required. An attacker who can submit a crafted remote file identifier to the FileCopyService controls both the output path and the written content. Placing a web-executable payload such as an .aspx file into a writable IIS virtual directory yields code execution within the IIS worker process. The scope remains unchanged, and the service account privileges define the resulting access.
No verified public exploit code is available. Refer to the vendor advisory linked above for technical details.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-93695
Indicators of Compromise
- Unexpected .aspx, .ashx, or .dll files appearing in IIS-served directories under the ShareFile Storage Zones Controller installation path
- FileCopyService log entries referencing remote file identifiers containing ..\, ../, or absolute path prefixes such as C:\
- New files written by the Storage Zones Controller service account outside the designated temporary staging directory
- IIS worker process (w3wp.exe) spawning unusual child processes such as cmd.exe, powershell.exe, or rundll32.exe
Detection Strategies
- Monitor file creation events in IIS content roots and compare against expected deployment baselines
- Alert on FileCopyService write operations where the resolved path exits the intended temporary directory
- Inspect ShareFile Storage Zones Controller logs for malformed or traversal-laden remote file identifiers
- Correlate web server process ancestry with endpoint telemetry to catch post-exploitation command execution
Monitoring Recommendations
- Enable file integrity monitoring on IIS virtual directories and Storage Zones Controller installation paths
- Forward IIS, Windows Security, and FileCopyService logs to a centralized analytics platform for correlation
- Baseline the service account's normal write locations and alert on deviations
- Track outbound network connections from w3wp.exe to identify webshell callbacks
How to Mitigate CVE-2026-93695
Immediate Actions Required
- Upgrade Progress ShareFile Storage Zones Controller to a version above 5.12.6 as specified in the vendor advisory
- Audit IIS-served directories for unauthorized executable files and remove any that are not part of a known deployment
- Restrict the Storage Zones Controller service account to the minimum filesystem permissions needed for normal operation
- Review FileCopyService and IIS logs for traversal patterns or anomalous file writes dating back to installation
Patch Information
Progress has published fixed versions and remediation guidance in the ShareFile Security Vulnerability Report. Administrators should apply the vendor-supplied update to all Storage Zones Controller instances and verify version strings after installation.
Workarounds
- Remove write permissions for the Storage Zones Controller service account on all IIS-served executable directories
- Place the controller's temporary staging directory on a filesystem path with no overlap to any IIS virtual directory
- Restrict network access to the Storage Zones Controller management and file transfer interfaces to trusted hosts only
- Disable or isolate affected controllers until the vendor patch can be applied
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

