{"answers":{"affected":"3 open source packages ship an affected version, including copyparty. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32108 in the wild and no public exploit code.","fix":"Upgrade copyparty to 1.20.12 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-32108 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-32108 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- copyparty (PyPI): affected all versions; fixed in 1.20.12\n- copyparty (PyPI): affected all versions; fixed in 1.20.12\n- copyparty (PyPI): affected all versions; fixed in 1.20.12\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32108/ (Markdown: https://insights.sbomify.com/CVE-2026-32108/index.md)","id":"CVE-2026-32108","markdown":"https://insights.sbomify.com/CVE-2026-32108/index.md","name":"CVE-2026-32108","record":{"aliases":["GHSA-67rw-2x62-mqqm","PYSEC-2026-31"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Copyparty file server","requires_auth":"low_privilege","summary":"Attackers can read sibling files in a shared folder via FTP/SFTP if shares are configured for single files, bypassing intended access restrictions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"copyparty","vendor":"9001"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Copyparty ftp/sftp: Sharing a single file did not fully restrict source-folder access","id":"CVE-2026-32108","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Copyparty has unexpected JavaScript execution via crafted URL to folder with `.prologue.html`","id":"CVE-2026-32109"},"packages":[{"ecosystem":"PyPI","fixed":["1.20.12"],"introduced":["0"],"last_affected":[],"package":"copyparty","purl":null,"source":"GHSA-67rw-2x62-mqqm"},{"ecosystem":"PyPI","fixed":["1.20.12"],"introduced":["0"],"last_affected":[],"package":"copyparty","purl":"pkg:pypi/copyparty","source":"GHSA-67rw-2x62-mqqm"},{"ecosystem":"PyPI","fixed":["1.20.12"],"introduced":["0"],"last_affected":[],"package":"copyparty","purl":"pkg:pypi/copyparty","source":"PYSEC-2026-31"}],"prev":{"headline":"xrdp: Fail-open privilege drop in sesexec — child processes may execute as root if setuid fails","id":"CVE-2026-32107"},"products":["copyparty"],"published":"2026-03-11","related":[{"cvss_score":7.8,"headline":"Cross-site scripting in n/a","id":"CVE-2023-41471","kev_date_added":null,"published":"2025-08-29"},{"cvss_score":7.5,"headline":"Copyparty is vulnerable to Regex Denial of Service (ReDoS) attacks through \"Recent Uploads\" page","id":"CVE-2025-54796","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":7.5,"headline":"Path traversal in copyparty","id":"CVE-2023-37474","kev_date_added":null,"published":"2023-07-14"},{"cvss_score":6.3,"headline":"copyparty Reflected XSS via Filter Parameter","id":"CVE-2025-54589","kev_date_added":null,"published":"2025-07-31"},{"cvss_score":6.3,"headline":"copyparty vulnerable to reflected cross-site scripting via k304 parameter","id":"CVE-2023-38501","kev_date_added":null,"published":"2023-07-25"},{"cvss_score":5.4,"headline":"Copyparty vulnerable to eflected cross-site scripting via setck parameter","id":"CVE-2026-27948","kev_date_added":null,"published":"2026-02-26"},{"cvss_score":5.4,"headline":"copyparty has a DOM-Based XSS vulnerability when displaying multimedia metadata","id":"CVE-2025-54423","kev_date_added":null,"published":"2025-07-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["9001"]},"summary":"Attackers can read sibling files in a shared folder via FTP/SFTP if shares are configured for single files, bypassing intended access restrictions.","url":"https://insights.sbomify.com/CVE-2026-32108/"}