# CVE-2026-126937: Zipline before 4.6.5 TOCTOU Race Condition via /api/setup


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/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-jc78-2hw2-8h3g, GHSA-wgjv-p9mm-qw77

## What is CVE-2026-126937?

CVE-2026-126937 is a critical vulnerability in diced zipline, published on 13 Nov 2026. 

### Official description

Zipline before 4.6.5 contains a TOCTOU race condition in the POST /api/setup endpoint that allows unauthenticated attackers to create multiple SUPERADMIN accounts by racing concurrent requests before the firstSetup flag is reset. Attackers can send simultaneous requests with spoofed X-Forwarded-For headers during the argon2 hashing window to gain full administrative control of the instance.

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

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


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

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

## Is CVE-2026-126937 being exploited?

There is no known exploitation of CVE-2026-126937 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-126937 PoC: Zipline 4.6.4 POST /api/setup checks firstSetup, hashes with argon2 and resets the flag non-atomically - 20 barrier-synced requests with spoofed X-Forwarded-For created 15 SUPERADMINs (323 ms window); 4.6.5's advisory lock yields exactly one. (github_poc): https://github.com/googlesky/CVE-2026-126937

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126937 is a critical vulnerability in diced zipline, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-126937 in the wild and no public exploit code.

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

## Sources

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

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