ZIPLINE · CVE-2026-126949 · Package
NO FIX YET · SEE WHAT TO DO
Zipline through 4.4.0 fails to sanitize file names in its PATCH /api/user/files/:id rename endpoint. An authenticated user can submit a name such as ../uploads/victim.txt to overwrite other users' uploaded files.
first public Jan 20, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted Zipline 4.4.0 or earlier that stores uploads on the Local filesystem datasource and has more than one authenticated user. Any user who can rename files can overwrite another user's upload by renaming their own file to ../uploads/<victim name>. Single-user instances, or ones where every account is trusted, can mostly skip it. The advisory names no patched version.
Not affected if no-untrusted-users, s3-datasource, single-user
Who cares local-datasource, path-traversal, self-hosted, zipline
4.4.0 or earlier with the Local datasource (DATASOURCE_TYPE=local, uploads on disk)? Then you are in scope4.4.0 and the release notes do not say whether the rename path was fixedZipline through 4.4.0 contains a path traversal vulnerability in the PATCH /api/user/files/:id rename endpoint that allows authenticated users to overwrite existing uploads by supplying unsanitized names. Attackers can submit names like ../uploads/victim.txt that bypass the raw-string database uniqueness check but normalize via path.join(), causing fs.rename() to replace other files' contents.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
v4.8.3 (Nov 8) do not name this bug in their notes, so a fix is unconfirmed