# CVE-2025-71461: Zipline before 4.0.2 Predictable Filenames via Math.random State Recovery

> Attackers can predict other users' upload filenames in Zipline by recovering Math.random state, exposing private uploads.

- **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
- **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:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-6rg9-q9ww-w2rw, GHSA-vf9w-pwwq-jwvx

## What is CVE-2025-71461?

CVE-2025-71461 is a medium-severity weak cryptography vulnerability in diced zipline, published on 13 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zipline before 4.0.2 contains a predictable filename vulnerability that allows attackers to infer other users' upload filenames by recovering the Math.random generator state. Attackers with five consecutive gfycat-style filenames can reconstruct the random state to predict previous and future filenames until the instance restarts, exposing private uploads.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2025-71461?

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


## How do I fix CVE-2025-71461?

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

## Is CVE-2025-71461 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71461 and fix it if it is affected.

What it is: CVE-2025-71461 is a medium-severity weak cryptography vulnerability in diced zipline, published on 13 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-2025-71461 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-2025-71461/ (Markdown: https://insights.sbomify.com/CVE-2025-71461/index.md)
```

## Sources

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

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