How severe is GHSA-pxvw-4w88-6x95?

No CVSS score has been assigned to GHSA-pxvw-4w88-6x95 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pxvw-4w88-6x95?

GHSA-pxvw-4w88-6x95 affects the following packages: copyparty (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-pxvw-4w88-6x95?

Update copyparty to 1.19.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pxvw-4w88-6x95 is resolved across your whole dependency graph.

How do I detect GHSA-pxvw-4w88-6x95 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for copyparty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pxvw-4w88-6x95 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-pxvw-4w88-6x95 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pxvw-4w88-6x95 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pxvw-4w88-6x95?

GHSA-pxvw-4w88-6x95 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pxvw-4w88-6x95?

GHSA-pxvw-4w88-6x95 is classified as CWE-552 (CWE-552), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pxvw-4w88-6x95 published, and has it been updated?

GHSA-pxvw-4w88-6x95 was published on September 9, 2025 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

copyparty: Sharing a single file does not fully restrict access to other files in source folderGHSA-pxvw-4w88-6x95

Fix: 9001/copyparty@e0a92ba

GHSA-pxvw-4w88-6x95 is a CWE-552 vulnerability in copyparty. A fix is available for copyparty — see the affected versions and patch details below.

Also known asCVE-2025-58753PYSEC-2026-1279

Published

Sep 9, 2025

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pxvw-4w88-6x95.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍copyparty

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Copyparty is a portable file server. In versions prior to 1.19.8, there was a missing permission-check in the shares feature (the shr global-option). When a share was created for just one file inside a folder, it was possible to access the other files inside that folder by guessing the filenames. It was not possible to descend into subdirectories in this manner; only the sibling files were accessible. This issue did not affect filekeys or dirkeys. Version 1.19.8 fixes the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`copyparty`	all versions	1.19.8`pip install --upgrade 'copyparty==1.19.8'`

Affected Products

1 product · 1 configurations

Application

copyparty9001

< 1.19.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for copyparty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update copyparty to 1.19.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pxvw-4w88-6x95 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

There was a missing permission-check in the shares feature (the `shr` global-option). When a share is created for just one file inside a folder, it was possible to access the other files inside that folder by guessing the filenames. It was not possible to descend into subdirectories in this manner; only the sibling files were accessible. This issue did not affect filekeys or dirkeys.