In Progress ShareFile Storage Zones Controller v5.12.6 and below, FileCopyService uses a remote file identifier when constructing a local temporary file path without enforcing containment. This can cause FileCopyService to write attacker-controlled content to filesystem locations writable by the service account. This can result in remote code execution when an executable IIS-served directory is writable.
Severity
CVSS 3.1
7.4 high
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2%(unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path traversal) CWE-73External Control of File Name or Path
Show the promptExplain CVE-2026-93695 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93695?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93695?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-93695 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
progress:sharefile storage zones controller
Versions
From the CNA's record in the CVE List.
Product
Affected
Progress ShareFile Storage Zones Controller
through 5.12.6
Attack patterns (CAPEC)
CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
CAPEC-126 Path Traversal Likelihood: High · Severity: Very High
CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
CAPEC-72 URL Encoding Likelihood: High · Severity: High
CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.