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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pxvw-4w88-6x95?

O3 pinpoints whether GHSA-pxvw-4w88-6x95 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.3%, placing it in the 26th 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.

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 September 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-pxvw-4w88-6x95

copyparty: Sharing a single file does not fully restrict access to other files in source folder

Also known asCVE-2025-58753

Published

Sep 9, 2025

Updated

Sep 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk26th percentile+0.32%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`copyparty`	all versions	1.19.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for copyparty. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pxvw-4w88-6x95 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-pxvw-4w88-6x95. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

O3 Security · Impact-Aware SCA

Is GHSA-pxvw-4w88-6x95 in your dependencies?

O3 detects GHSA-pxvw-4w88-6x95 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works