# CVE-2026-126938: Zipline before 4.6.4 Upload Quota Bypass via Forged Content-Range Headers


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/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-27fc-v9hw-m665, GHSA-fp8p-hf8g-fw65

## What is CVE-2026-126938?

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

### Official description

Zipline before 4.6.4 contains a resource allocation vulnerability that allows authenticated users to bypass chunked-upload size and quota checks by forging Content-Range offsets and totals. Attackers can send tiny chunks to the partial upload endpoint with large declared offsets, causing the server to create oversized files and exhaust disk space.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-126938 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-126938 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126938 is a high-severity vulnerability in diced zipline, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-126938 exists.

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-126938/ (Markdown: https://insights.sbomify.com/CVE-2026-126938/index.md)
```

## Sources

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

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