Skip to main content
CVE Radar
highDenial of Service

CVE-2026-126938

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

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.

Published Updated Sources: diced (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

ahead of 0% of scored CVEs

Affects

Diced

2 products listed

CVSS base

7.1

high · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade Zipline to a fixed release (4.6.4). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Affected vendors, products and versions
VendorProductVersionsStatus
Dicedzipline0 to < 4.6.4Vulnerable
Dicedzipline4.6.4Patched

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

None

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Every CVSS base score collected, by source and version
ScoreVersionSeverityExpl.ImpactSource
7.1CVSS 4.0highn/an/adiced (CNA)
7.1CVSS 3.1highn/an/adiced (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-770 · Allocation of Resources Without Limits or Throttling

  • DoS: Resource Consumption (CPU)
  • DoS: Resource Consumption (Memory)
  • DoS: Resource Consumption (Other)

Mitigation: Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.

Weakness & attack patterns

  • CWE-770

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-528 · XML FloodCAPEC-230 · XML Nested PayloadsCAPEC-496 · ICMP FragmentationCAPEC-493 · SOAP Array BlowupCAPEC-487 · ICMP FloodCAPEC-147 · XML Ping of the DeathCAPEC-495 · UDP FragmentationCAPEC-486 · UDP FloodCAPEC-489 · SSL FloodCAPEC-469 · HTTP DoSCAPEC-231 · Oversized Serialized Data PayloadsCAPEC-494 · TCP Fragmentation
  • T1498.001Network Denial of Service: Direct Network Flood
  • T1499Endpoint Denial of Service
  • T1499.003Endpoint Denial of Service: Application Exhaustion Flood

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable Zipline.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 7.1 (AV:N)

    Nov 13, 2026 · NVD

  3. Initial · CVE published

    Nov 13, 2026 · NVD

  4. CVE published by MITRE.

    Nov 13, 2026 · SOCRadar CTI

References

2 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-126938 is Zipline before 4.6.4 Upload Quota Bypass via Forged Content-Range Headers, a high vulnerability affecting Zipline from Diced. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-126938. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-126938. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.