dbcve.org
CopypartyApplication · 9001

CVE-2026-32108

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 1.20.12 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Copyparty is a portable file server. Prior to 1.20.12, there was a missing permission-check in the shares feature (the shr global-option). This vulnerability only applies when the shares feature is used for the specific purpose of creating a share of just a single file inside a folder or either the FTP or SFTP server is enabled, and also made publicly accessible. Given these conditions, when a user is browsing a share through either FTP or SFTP (not http or https), they can gain read-access to the remaining files inside the shared folder by guessing/bruteforcing the filenames. It was not possible to descend into subdirectories in this manner; only the sibling files were accessible. This vulnerability is similar to CVE-2025-58753 which was previously fixed for HTTP and HTTPS, but not for FTP. The FTPS server did not yet exist at that time. This vulnerability is fixed in 1.20.12.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Copyparty prior to 1.20.12 has a missing permission check in the shares feature (shr global-option). When FTP or SFTP servers are enabled and publicly accessible, users browsing a share containing a single file inside a folder via FTP/SFTP can bypass authorization to read sibling files by guessing/bruteforcing filenames. This is similar to CVE-2025-58753 which was fixed for HTTP/HTTPS but not for the FTP/SFTP protocols.

MitigationUpgrade to Copyparty version 1.20.12 or later to obtain the patched version, or disable FTP/SFTP server access if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CopypartyApplication
Affected:< 1.20.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Copyparty version
    Run 'copyparty --version' or check the installed package version to determine if it is prior to 1.20.12
    Affected if The installed version is less than 1.20.12
  2. Verify FTP server is enabled
    Inspect the copyparty startup command or configuration file for FTP server flags (typically -ftp or similar)
    Affected if FTP server is enabled in the Copyparty configuration
  3. Verify SFTP server is enabled
    Inspect the copyparty startup command or configuration file for SFTP server flags (typically -sftp or similar)
    Affected if SFTP server is enabled in the Copyparty configuration
  4. Confirm shares (shr) are configured
    Inspect the copyparty configuration for the 'shr' global option which enables the shares feature
    Affected if The shares feature (shr) is configured and active
  5. Check FTP/SFTP network accessibility
    Verify whether the FTP or SFTP service is bound to a publicly accessible interface or IP address
    Affected if FTP or SFTP services are exposed to untrusted network access

If Copyparty version is below 1.20.12 and FTP or SFTP servers are enabled with shares configured and publicly accessible, the environment is vulnerable to authorization bypass via filename guessing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.20.12 or later
Fixed in 1.20.12
Interim mitigation

Upgrade to Copyparty version 1.20.12 or later to obtain the patched version, or disable FTP/SFTP server access if not required.

Recommended fix High confidence

1.20.12

  1. Check the current installed version of Copyparty using 'pip show copyparty' or the --version flag
  2. Upgrade Copyparty to version 1.20.12 using 'pip install copyparty==1.20.12' or 'pip install --upgrade copyparty==1.20.12'
  3. Verify the upgrade was successful by checking the version again
  4. Restart the Copyparty service if it is running as a daemon
  5. Confirm the shares feature (shr option) now properly enforces authorization for FTP/SFTP access

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Copyparty Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32108 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data