CVE
Zipline unauthorized folder changes via IDOR in PATCH and DELETE
Affects Zipline versions before 4.5.0 (4.4.4 and earlier), where authenticated users can rename, publish, or delete other users' folders. Fixed in 4.5.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.5.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Zipline version before 4.5.0 (affected versions 4.4.4 and earlier)
- 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.44% · 38th 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? →
- 17/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 (diced/zipline) before version 4.5.0 is affected by a flaw in its folder PATCH and DELETE handlers, which fail to check that the requesting user owns the folder. A remote attacker with a low-privilege user account can exploit this by supplying another user's folder ID to rename that folder, make it public, enable uploads to it, or delete it.
Read the original description
Zipline before 4.5.0 contains an insecure direct object reference vulnerability caused by missing ownership verification in the PATCH and DELETE handlers for /api/user/folders/:id. Authenticated attackers can supply another user's folder ID to rename it, make it public, enable uploads, or delete it.
Who should check
Teams running diced Zipline before 4.5.0 on instances with multiple user accounts that use folders
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
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Zipline version before 4.5.0 (affected versions 4.4.4 and earlier)Upgrade to a fixed version: 4.5.0.
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-2026-126948 (Zipline before 4.5.0 IDOR via Folder PATCH and DELETE Endpoints), 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-2026-126948 (entry last updated 2026-11-13):
Affected:
- diced zipline: fixed in 4.5.0
Fixed versions: 4.5.0.
Conditions (all must be true for the bug to be hit):
- Zipline version before 4.5.0 (affected versions 4.4.4 and earlier) (source: https://www.vulncheck.com/advisories/zipline-before-4.5.0-idor-via-folder-patch-and-delete-endpoints)
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-2026-126948 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126948 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-fgwh-2pc5-wr73
- https://www.vulncheck.com/advisories/zipline-before-4.5.0-idor-via-folder-patch-and-delete-endpoints
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-2026-126948
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-2026-126948"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- diced zipline
fixed in 4.5.0
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-2026-126948
Is CVE-2026-126948 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 can supply another user's folder ID to the folder PATCH and DELETE endpoints. This lets them rename that folder, make it public, enable uploads on it, or delete it.Source: vulncheck.com
Which versions are affected by CVE-2026-126948?
zipline: before 4.5.0.Source: cve.now feed data
Am I affected, and how do I check?
Zipline versions before 4.5.0, which the advisory describes as 4.4.4 and earlier, are affected. Compare the installed Zipline version with 4.5.0 to see where a given install falls.Source: vulncheck.com
How do I fix CVE-2026-126948?
Upgrade Zipline to version 4.5.0 or later, which is the listed fixed version.Source: vulncheck.com