CVE
Zipline arbitrary file write via upload filename header
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Zipline uses the local storage datasource Attacker has upload access to the Zipline instance
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.53% · 45th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Zipline through 4.3.2 contains a path traversal vulnerability that allows authenticated uploaders to write files outside the upload directory by supplying traversal sequences in the x-zipline-filename header. Attackers using the local datasource can create or overwrite files writable by the Zipline process, corrupting application data or disrupting service.
Who should check
Teams running diced zipline 4.3.2 or earlier with the local storage datasource and upload access enabled.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Zipline uses the local storage datasource Attacker has upload access to the Zipline instanceWorkaround: The facts do not name a workaround. Limiting upload access to trusted users, or avoiding the local storage datasource, would remove the conditions this bug depends on.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2025-71459 (Zipline through 4.3.2 Path Traversal via x-zipline-filename Header), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2025-71459 (entry last updated 2026-11-13):
Affected:
- diced zipline: through 4.3.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Zipline uses the local storage datasource (source: https://github.com/diced/zipline/security/advisories/GHSA-4jm6-mgwv-fq63)
- Attacker has upload access to the Zipline instance (source: https://github.com/diced/zipline/security/advisories/GHSA-4jm6-mgwv-fq63)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2025-71459 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-71459 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/diced/zipline/security/advisories/GHSA-4jm6-mgwv-fq63
- https://www.vulncheck.com/advisories/zipline-through-4.3.2-path-traversal-via-x-zipline-filename-header
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2025-71459
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2025-71459"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- diced zipline
through 4.3.2
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-71459
Is CVE-2025-71459 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user who can upload files can supply a crafted x-zipline-filename header that makes Zipline build a storage path that leaves the configured upload directory. Attacker-controlled content can then be written outside the intended storage directory, which can corrupt application data or disrupt service.Source: github.com
Which versions are affected by CVE-2025-71459?
zipline: through 4.3.2.Source: cve.now feed data
Am I affected, and how do I check?
Zipline through 4.3.2 is affected when it uses the local storage datasource and the user has upload access. To check, look at the Zipline version in use and confirm whether the datasource setting is local.Source: github.com
How do I fix CVE-2025-71459?
No fixed version is listed in the facts for this vulnerability, so no upgrade target can be given. Check the vendor's advisory for a patch or updated version.Source: github.com
What if there's no patch?
The facts do not name a workaround. Limiting upload access to trusted users, or avoiding the local storage datasource, would remove the conditions this bug depends on.Source: github.com