# CVE-2026-126935: Zipline before 4.8.0 maxViews Limit Bypass via Race Condition

> Attackers with a file link can race view counts to read view-limited or delete-on-max-views files in Zipline.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-7xv9-wr46-j578, GHSA-9m43-j2p8-v7v3

## What is CVE-2026-126935?

CVE-2026-126935 is a medium-severity race condition vulnerability in diced zipline, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zipline before 4.8.0 contains a race condition vulnerability in src/server/routes/raw/[id].ts that allows remote attackers to bypass file maxViews limits through non-atomic view counting. Attackers holding a file link can send parallel requests that read the same pre-increment count, viewing view-limited or delete-on-max-views files beyond their limit.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-126935 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126935 is a medium-severity race condition vulnerability in diced zipline, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-126935 exists.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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