Skip to main content
Menu
CVEs

CVE

Zipline arbitrary file deletion via path traversal in uploads

Affects Zipline 4.4.0 and earlier on deployments that use LocalDatasource or a datasource delete implementation that does not constrain keys. No fixed version is listed.

CVE-2026-126950EUVD-2026-125115GHSA-MHGX-Q5QW-7237GHSA-2WFM-PRG7-X586

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:H/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 or earlier (affected versions listed as 4.4.0). Deployment uses LocalDatasource, or a datasource delete implementation that does not constrain keys, and authenticated users can upload files and set expiry.

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

Summary

Zipline through 4.4.0 contains a path traversal vulnerability that allows authenticated attackers to delete arbitrary server files by injecting traversal sequences via the x-zipline-file-extension header. Attackers can upload a file with a poisoned stored name and short expiry so LocalDatasource deletion removes chosen files, causing denial of service or data loss.

Who should check

Teams running Zipline 4.4.0 or earlier with LocalDatasource, where authenticated users can upload files and set expiry.

“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 or earlier (affected versions listed as 4.4.0). Deployment uses LocalDatasource, or a datasource delete implementation that does not constrain keys, and authenticated users can upload files and set expiry.
  • Workaround: The checked facts give no workaround. The conditions point to the two factors involved: the LocalDatasource or unconstrained delete implementation, and authenticated users being able to upload files and set expiry.

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-126950 (Zipline through 4.4.0 Path Traversal Arbitrary File Delete via x-zipline-file-extension), 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-126950 (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 or earlier (affected versions listed as 4.4.0). (source: https://www.vulncheck.com/advisories/zipline-through-4.4.0-path-traversal-arbitrary-file-delete-via-x-zipline-file-extension)
- Deployment uses LocalDatasource, or a datasource delete implementation that does not constrain keys, and authenticated users can upload files and set expiry. (source: https://github.com/diced/zipline/security/advisories/GHSA-2wfm-prg7-x586)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-126950 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126950 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-2wfm-prg7-x586
- https://www.vulncheck.com/advisories/zipline-through-4.4.0-path-traversal-arbitrary-file-delete-via-x-zipline-file-extension
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-126950
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-126950"}.

Public exploit activity

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

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-126950

Is CVE-2026-126950 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?

A path traversal flaw lets the delete function remove arbitrary files on the server, not only uploaded files. The impact is denial of service or removal of security-critical data.Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-126950?

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

Am I affected, and how do I check?

Zipline version 4.4.0 or earlier is affected. The setup also matters: deployments using LocalDatasource, or a datasource delete implementation that does not constrain keys, where authenticated users can upload files and set expiry. Check the installed Zipline version and the configured datasource to compare against these conditions.Source: vulncheck.com, github.com

How do I fix CVE-2026-126950?

The checked facts name no fixed version or vendor patch, so no upgrade target can be given. Check the advisory for an update.Source: vulncheck.com, github.com

What if there's no patch?

The checked facts give no workaround. The conditions point to the two factors involved: the LocalDatasource or unconstrained delete implementation, and authenticated users being able to upload files and set expiry.Source: vulncheck.com, github.com