Skip to main content
VulnerabilityPublished

CVE-2026-126939: diced zipline · Information Exposure

Affects diced ziplineSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.6.4 when convenient.

Data as of 13 Nov 2026, 10:58 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.15.3
Patch
Available – fixed in 4.6.4
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade diced zipline to 4.6.4.

Affected software

ProductAffectedFixed in
dicedziplineAffected
  • <4.6.4
Fixed in
  • 4.6.4
npmziplinepkg:npm/ziplineOther threatsAffected
  • <4.6.4
Fixed in
  • 4.6.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Zipline to version 4.6.4 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated.

Description

Zipline versions prior to 4.6.4 contain an information disclosure vulnerability in the GET /api/server/folder/:id endpoint. This flaw allows unauthenticated attackers who know a folder's UUID to enumerate file details such as names, IDs, MIME types, sizes, and view counts in non-public upload-only folders by manipulating the page query parameter. The vulnerability is fixed in version 4.6.4.

References

Community reviews

Loading reviews…