# CVE-2026-126950: Zipline through 4.4.0 Path Traversal Arbitrary File Delete via x-zipline-file-extension


- **Severity:** High 7.0 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-2wfm-prg7-x586, GHSA-mhgx-q5qw-7237

## What is CVE-2026-126950?

CVE-2026-126950 is a high-severity vulnerability in diced zipline, published on 13 Nov 2026. 

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-126950?


## How do I fix CVE-2026-126950?

No fix has been published for CVE-2026-126950 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126950 being exploited?

There is no known exploitation of CVE-2026-126950 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126950 and fix it if it is affected.

What it is: CVE-2026-126950 is a high-severity vulnerability in diced zipline, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-126950 in the wild and no public exploit code.

Affected product: diced zipline. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126950/ (Markdown: https://insights.sbomify.com/CVE-2026-126950/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126950
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126950
- OSV: https://osv.dev/vulnerability/CVE-2026-126950

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126950/
Summaries are generated and may contain mistakes; the official description above is the record.
