Skip to main content
Menu
CVEs

CVE

Zipline path traversal in file rename API enables file overwrite

Affects Zipline 4.4.0 and earlier when uploads are stored on the local filesystem. The checked facts give no vendor rating and no fixed version.

CVE-2026-126949EUVD-2026-125116GHSA-6H3M-PW73-74R6GHSA-RW9M-7MVM-6GXP

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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

7.0HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Zipline version 4.4.0 and earlier (affected versions 4.4.0). Local datasource enabled, with uploads stored on the local filesystem.

Published
Last modified
Reference
Last checked
0.45% · 39th percentile
20/100
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

Zipline from diced has a path traversal flaw in its file rename endpoint (PATCH /api/user/files/:id) that lets an attacker overwrite other users' uploaded files. The attack can be carried out remotely over the network, but only after logging in with high privileges, by submitting crafted file names such as ../uploads/victim.txt.

Original description

Zipline 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.

Who should check

Teams running diced zipline 4.4.0 or earlier with the Local datasource, where authenticated users can rename files.

“Affecting zipline <= 4.4.0”

vulncheck.com

cve.now Index

20cve.now Index 20 of 100 · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7/10CVSS 7.0
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 27 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Zipline version 4.4.0 and earlier (affected versions 4.4.0). Local datasource enabled, with uploads stored on the local filesystem.
  • Workaround: The checked facts name no workaround. Because the issue requires local filesystem storage, the facts do not confirm whether changing the storage setup would help.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126949 (Zipline through 4.4.0 Path Traversal File Overwrite via PATCH /api/user/files/:id), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126949 (entry last updated 2026-11-13):
Affected:
- diced zipline: through 4.4.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Zipline version 4.4.0 and earlier (affected versions 4.4.0). (source: https://www.vulncheck.com/advisories/zipline-through-4.4.0-path-traversal-file-overwrite-via-patch-api-user-files-id)
- Local datasource enabled, with uploads stored on the local filesystem. (source: https://github.com/diced/zipline/security/advisories/GHSA-rw9m-7mvm-6gxp)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-126949 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126949 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/diced/zipline/security/advisories/GHSA-rw9m-7mvm-6gxp
- https://www.vulncheck.com/advisories/zipline-through-4.4.0-path-traversal-file-overwrite-via-patch-api-user-files-id
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126949
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126949"}.

Public exploit activity

100%0Nov 13Nov 17
  • EPSS: 0.45%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • diced zipline

    through 4.4.0

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126949

Is CVE-2026-126949 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An authenticated user can rename their own upload to a path containing traversal sequences. This overwrites existing uploaded files on disk, replacing the contents of other files.Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-126949?

zipline: through 4.4.0.Source: cve.now feed data

Am I affected, and how do I check?

Zipline 4.4.0 and earlier, when the local datasource is enabled and uploads are stored on the local filesystem. Check the installed Zipline version and whether the datasource is set to local storage.Source: vulncheck.com, github.com

How do I fix CVE-2026-126949?

The checked facts list no fixed version or vendor patch identifiers, so no upgrade target can be given. Check the vendor's advisory for a fix.Source: vulncheck.com, github.com

What if there's no patch?

The checked facts name no workaround. Because the issue requires local filesystem storage, the facts do not confirm whether changing the storage setup would help.Source: vulncheck.com, github.com