CVE-2026-126949: diced zipline · Path Traversal
Affects diced ziplineSource CVE Database V5
Not known to be exploited · CVSS 7.0 High.
Data as of 13 Nov 2026, 10:13 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.0 |
|---|
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dicedzipline | Affected
| Fixed in– |
AI-suggested
Users should check the vendor's advisory for updates and apply any official patches once available. Until then, restrict access to the rename endpoint to trusted users only and consider implementing additional input validation or sanitization on filenames to prevent directory traversal sequences.
Description
Zipline versions up to 4.4.0 have a path traversal vulnerability in the PATCH /api/user/files/:id rename endpoint. Authenticated users can exploit this flaw by submitting crafted filenames with directory traversal sequences (e.g., ../uploads/victim.txt) that bypass database uniqueness checks but are normalized by the system, allowing overwriting of arbitrary uploaded files.