# CVE-2026-32108: Copyparty ftp/sftp: Sharing a single file did not fully restrict source-folder access

> Attackers can read sibling files in a shared folder via FTP/SFTP if shares are configured for single files, bypassing intended access restrictions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-67rw-2x62-mqqm, PYSEC-2026-31

## What is CVE-2026-32108?

CVE-2026-32108 is a low-severity missing authorization vulnerability in 9001 copyparty, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-32108?

3 open source packages ship an affected version, including copyparty. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `copyparty` | PyPI | All versions | 1.20.12 |
| `copyparty` | PyPI | All versions | 1.20.12 |
| `copyparty` | PyPI | All versions | 1.20.12 |

Products: 9001 Copyparty.

## How do I fix CVE-2026-32108?

Upgrade copyparty to 1.20.12 or later.

## Is CVE-2026-32108 being exploited?

There is no known exploitation of CVE-2026-32108 in the wild and no public exploit code.

## Other vulnerabilities in 9001 copyparty

- [CVE-2023-41471](https://insights.sbomify.com/CVE-2023-41471/): Cross-site scripting in n/a (high 7.8)
- [CVE-2025-54796](https://insights.sbomify.com/CVE-2025-54796/): Copyparty is vulnerable to Regex Denial of Service (ReDoS) attacks through "Recent Uploads" page (high 7.5)
- [CVE-2023-37474](https://insights.sbomify.com/CVE-2023-37474/): Path traversal in copyparty (high 7.5)
- [CVE-2025-54589](https://insights.sbomify.com/CVE-2025-54589/): copyparty Reflected XSS via Filter Parameter (medium 6.3)
- [CVE-2023-38501](https://insights.sbomify.com/CVE-2023-38501/): copyparty vulnerable to reflected cross-site scripting via k304 parameter (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32108 and fix it if it is affected.

What it is: CVE-2026-32108 is a low-severity missing authorization vulnerability in 9001 copyparty, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32108 in the wild and no public exploit code.

Affected packages and fixed versions:
- copyparty (PyPI): affected all versions; fixed in 1.20.12
- copyparty (PyPI): affected all versions; fixed in 1.20.12
- copyparty (PyPI): affected all versions; fixed in 1.20.12

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-2026-32108/ (Markdown: https://insights.sbomify.com/CVE-2026-32108/index.md)
```

## Sources

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

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