# CVE-2026-126939: Zipline before 4.6.4 Unauthenticated File Listing via page Query Parameter


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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-gxr6-mx45-w66j, GHSA-jh6v-w5f3-8p4x

## What is CVE-2026-126939?

CVE-2026-126939 is a medium-severity vulnerability in diced zipline, published on 13 Nov 2026. 

### Official description

Zipline before 4.6.4 contains an information disclosure vulnerability in GET /api/server/folder/:id that allows unauthenticated attackers to list files in non-public upload-only folders. Attackers who know the folder UUID can supply the page query parameter to bypass the metadata-only early return and enumerate file names, IDs, MIME types, sizes, and view counts.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-126939 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126939 is a medium-severity vulnerability in diced zipline, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-126939 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-126939/ (Markdown: https://insights.sbomify.com/CVE-2026-126939/index.md)
```

## Sources

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

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