CVE-2026-25059 is a high-severity (CVSS 8.8) Path Traversal vulnerability in github.com/OpenListTeam/OpenList/v4. A fix is available for github.com/OpenListTeam/OpenList/v4 — see the affected versions and patch details below.
OpenList affected by Path Traversal in file copy and remove handlers
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25059.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-25059 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/OpenListTeam/OpenList/v4Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The application contains a Path Traversal vulnerability (CWE-22) in multiple file operation handlers. 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.
Details
The application contains a Path Traversal vulnerability (CWE-22) 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.
func FsRemove(c *gin.Context) {
// ...
for _, name := range req.Names {
err := fs.Remove(c, stdpath.Join(reqDir, name))
func FsCopy(c *gin.Context) {
// ...
if !req.Overwrite {
for _, name := range req.Names {
if res, _ := fs.Get(c.Request.Context(), stdpath.Join(dstDir, name), &fs.GetArgs{NoLog: true}); res != nil {
PoC
Scenario: A normal user ("alice") bypasses directory restrictions to read files outside her authorized path.
Environment setup:
- Local storage mount as '/local'.
- An admin file "adminsecret.txt" is placed under /local
- Alice has base path '/local/alice'.
https://github.com/user-attachments/assets/5d73bbec-29e5-4c52-8af3-4c70b26d9d0e
Impact
This vulnerability enables privilege escalation within shared storage environments. An authenticated attacker with basic file operation permissions (remove/copy) can bypass directory-level authorisation controls when multiple users exist within the same storage mount.
Attack Requirements:
- Authenticated user account (not guest)
- Basic file operation permissions (remove/copy)
- Multi-user environment within the same storage mount
- Knowledge (or ability to guess) the target file's name and path
Consequences:
- Unauthorised data access: Read, copy, and exfiltrate files from other users' directories
- Data destruction: Delete files belonging to other users
Note
This vulnerability was discovered by:
- XlabAI Team of Tencent Xuanwu Lab
- Atuin Automated Vulnerability Discovery Engine
CVE and credit are preferred.
If users have any questions regarding the vulnerability details, please feel free to reach out for further discussion. Email [email protected].
The security industry standard 90+30 disclosure policy is followed. Should the aforementioned vulnerabilities remain unfixed after 90 days of submission, all information about the issues will be publicly disclosed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/OpenListTeam/OpenList/v4 | all versions | 4.1.10go get github.com/OpenListTeam/OpenList/v4@v4.1.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/OpenListTeam/OpenList/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/OpenListTeam/OpenList/v4 to 4.1.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25059 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-25059 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-25059. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-25059 in your dependencies?
O3 Security finds CVE-2026-25059 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.