How severe is GHSA-f5pf-q7c7-m3vv?

No CVSS score has been assigned to GHSA-f5pf-q7c7-m3vv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f5pf-q7c7-m3vv?

GHSA-f5pf-q7c7-m3vv affects the following packages: cyberdrop-dl-patched (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-f5pf-q7c7-m3vv?

Update cyberdrop-dl-patched to 9.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5pf-q7c7-m3vv is resolved across your whole dependency graph.

How do I detect GHSA-f5pf-q7c7-m3vv in my PyPI dependencies?

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

How do I mitigate GHSA-f5pf-q7c7-m3vv if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-f5pf-q7c7-m3vv actively exploited in the wild?

No public exploit code has been indexed for GHSA-f5pf-q7c7-m3vv 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-f5pf-q7c7-m3vv?

GHSA-f5pf-q7c7-m3vv has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th 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-f5pf-q7c7-m3vv?

GHSA-f5pf-q7c7-m3vv is classified as Improper Input Validation (CWE-20), Information Exposure (CWE-200). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f5pf-q7c7-m3vv published, and has it been updated?

GHSA-f5pf-q7c7-m3vv was published on July 15, 2026 and was last updated on July 23, 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

Pixeldrain API key shared with unverified thirdparty sitesGHSA-f5pf-q7c7-m3vv

Fix: Cyberdrop-DL/cyberdrop-dl@4479555

GHSA-f5pf-q7c7-m3vv is a Improper Input Validation vulnerability in cyberdrop-dl-patched. A fix is available for cyberdrop-dl-patched — see the affected versions and patch details below.

Also known asCVE-2026-54254PYSEC-2026-3460

Published

Jul 15, 2026

Updated

Jul 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 11, 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-f5pf-q7c7-m3vv.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍cyberdrop-dl-patched

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

Summary

When processing Pixeldrain URLs, cyberdrop-dl-patched could send an Authorization header that includes the user's API key to unverified hosts.

Details

Pixeldrain offers several alternative domains in case the user's ISP blocks the primary domain. To support this, requests made by cyberdrop-dl-patched are not hardcoded and will use the same host as the input URL for API requests.

cyberdrop-dl-patched matches URLs to a crawler based on their host. If the host contains a crawler's supported host as a sub-string, it will match to that crawler.

An URL from a malicious domain (ex: https://evil-pixeldrain.com) would successfully match to the Pixeldrain crawler and cyberdrop-dl-patched will blindly use that host for any API request (https://evil-pixeldrain.com/api), leaking the user's API key to the malicious actor via the Authorization header.

Impact

Anyone who has setup a Pixeldrain API key with cyberdrop-dl-patched and uses cyberdrop-dl-patched on sites that could spawn downloads for other sites (ex: forums, Wordpress, Pixeldrain itself, etc...)

Patches

cyberdrop-dl-patched v9.14.0 fixes this issue by rejecting any Pixedrain URL if the host does not match an official domain exactly.

Workarounds

It's recommended to upgrade cyberdrop-dl-patched to version v9.14.0

Anyone who has used a Pixeldrain API key with cyberdrop-dl-patched should consider them compromised and delete them from their Pixeldrain account.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`cyberdrop-dl-patched`	≥ 8.5.0&&< 9.14.0	9.14.0`pip install --upgrade 'cyberdrop-dl-patched==9.14.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cyberdrop-dl-patched, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cyberdrop-dl-patched to 9.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5pf-q7c7-m3vv is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Summary When processing Pixeldrain URLs, `cyberdrop-dl-patched` could send an `Authorization` header that includes the user's API key to unverified hosts. ### Details Pixeldrain offers several alternative domains in case the user's ISP blocks the primary domain. To support this, requests made by `cyberdrop-dl-patched` are not hardcoded and will use the same host as the input URL for API requests. `cyberdrop-dl-patched` matches URLs to a crawler based on their host. If the host contains a crawler's supported host as a sub-string, it will match to that crawler. An URL from a malicious

O3 Security · Impact-Aware SCA

Is GHSA-f5pf-q7c7-m3vv in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works