Skip to main content
VulnerabilityPublished Updated

CVE-2026-25059: OpenListTeam OpenList · Path Traversal

Affects OpenListTeam OpenListSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 4.1.10 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Upgrade OpenList and openlistteam/OpenList to 4.1.10.

Affected software

ProductAffectedFixed in
OpenListTeamOpenListAffected
  • <4.1.10
Fixed in
  • 4.1.10
GitHubopenlistteam/OpenListpkg:github/openlistteam/OpenListOther threatsAffected
  • <4.1.10
Fixed in
  • 4.1.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade OpenList to version 4.1.10 or later, where this vulnerability is patched. Until patching is feasible, implement strict access controls to limit authenticated user permissions, minimizing the risk of privilege abuse. Monitor file operation logs for unusual deletion, renaming, or copying activities indicative of traversal exploitation. Employ application-layer firewalls or intrusion detection systems with custom rules to detect and block path traversal patterns in file operation requests. Conduct regular audits of file system permissions and user access rights within the storage mounts used by OpenList. Educate users on the importance of credential security to prevent unauthorized access. Additionally, consider isolating storage mounts per user or group to reduce the impact scope if traversal occurs. Finally, integrate vulnerability scanning and penetration testing focused on path traversal vectors in the software supply chain to detect similar issues proactively.

Description

OpenList Frontend is a UI component for OpenList. Prior to 4.1.10, the application contains path traversal vulnerability in multiple file operation handlers in server/handles/fsmanage.go. Filename components in req.Names are directly concatenated with validated directories using stdpath.Join. This allows ".." sequences to bypass path restrictions, enabling users to access other users' files within the same storage mount and perform unauthorized actions such as deletion, renaming, or copying of files. An authenticated attacker can bypass directory-level authorisation by injecting traversal sequences into filename components, enabling unauthorised file removal and copying across user boundaries within the same storage mount. This vulnerability is fixed in 4.1.10.

References

Community reviews

Loading reviews…