Skip to main content
Menu
CVEs

CVE

Zipline denial of service in chunked upload quota checks

Affects Zipline versions before 4.6.4 on instances with chunked uploads enabled and users. Fixed in 4.6.4.

CVE-2026-126938EUVD-2026-125127GHSA-FP8P-HF8G-FW65

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

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

7.1HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 4.6.4
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Chunked uploads are enabled on the instance Zipline version 4.6.3 or earlier

Published
Last modified
Reference
Last checked
0.41% · 35th percentile
30/100
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

Summary

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.

Who should check

Teams running self-hosted Zipline 4.6.3 or earlier with chunked uploads enabled and user accounts that can upload files.

“Any instance with chunking with users”

github.com

cve.now Index

30cve.now Index 30 of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

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

What to do

  • Check whether your setup matches what the bug needs.

    Chunked uploads are enabled on the instance Zipline version 4.6.3 or earlier
  • Upgrade to a fixed version: 4.6.4.

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-126938 (Zipline before 4.6.4 Upload Quota Bypass via Forged Content-Range Headers), 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-126938 (entry last updated 2026-11-13):
Affected:
- diced zipline: fixed in 4.6.4
Fixed versions: 4.6.4.
Conditions (all must be true for the bug to be hit):
- Chunked uploads are enabled on the instance (source: https://github.com/diced/zipline/security/advisories/GHSA-fp8p-hf8g-fw65)
- Zipline version 4.6.3 or earlier (source: https://www.vulncheck.com/advisories/zipline-before-4.6.4-upload-quota-bypass-via-forged-content-range-headers)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126938 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126938 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-fp8p-hf8g-fw65
- https://www.vulncheck.com/advisories/zipline-before-4.6.4-upload-quota-bypass-via-forged-content-range-headers
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-126938
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-126938"}.

Public exploit activity

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

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

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • diced zipline

    fixed in 4.6.4

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

Is CVE-2026-126938 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An authenticated user can send forged Content-Range headers during an upload, and Zipline trusts the offset in them. This lets a user bypass upload size and quota checks, so the server can create oversized files and exhaust disk space.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-126938?

zipline: before 4.6.4.Source: cve.now feed data

Am I affected, and how do I check?

Zipline versions before 4.6.4 are affected, but only on instances where chunked uploads are enabled and users can upload. To check, look at the installed Zipline version and whether chunked uploads are enabled on the instance.Source: github.com, vulncheck.com

How do I fix CVE-2026-126938?

Upgrade Zipline to version 4.6.4, which is the listed fixed version.Source: github.com, vulncheck.com