CVE-2024-41255: filestash · Insecure Default Variable Initialization
Affects filestashSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfilestash/filestashpkg:github/filestash/filestashOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-41255, organizations should first check for updates or patches from the filestash development team that address the TLS certificate verification issue. If an updated version is available, promptly apply it to ensure proper certificate validation is enforced. In the absence of an official patch, administrators should review and modify the filestash configuration or source code to enable strict TLS certificate verification for FTPS connections, ensuring that the client validates the server’s certificate chain and hostname. Network-level mitigations include deploying intrusion detection/prevention systems (IDS/IPS) to monitor for suspicious FTPS traffic patterns indicative of MitM attacks. Organizations should also educate users about the risks of interacting with untrusted networks and encourage the use of VPNs or other secure channels when accessing filestash services remotely. Additionally, implementing multi-factor authentication (MFA) for accessing filestash can reduce the risk of credential compromise. Regular security audits and penetration testing focused on FTPS implementations can help identify and remediate similar weaknesses proactively. Finally, consider alternative secure file transfer protocols or tools that enforce robust TLS validation if filestash cannot be secured promptly.
Description
filestash v0.4 is configured to skip TLS certificate verification when using the FTPS protocol, possibly allowing attackers to execute a man-in-the-middle attack via the Init function of index.go.