CVE-2026-54254
Fix: Cyberdrop-DL/cyberdrop-dl@4479555CVE-2026-54254 is a security vulnerability in cyberdrop-dl-patched. O3 Security confirms whether CVE-2026-54254 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Pixeldrain API key shared with unverified thirdparty sites
Real-World Exposure
cyberdrop-dl-patchedReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | cyberdrop-dl-patched | ≥ 8.5.0&&< 9.14.0 | 9.14.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cyberdrop-dl-patched. 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 cyberdrop-dl-patched to 9.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54254 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 CVE-2026-54254 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 CVE-2026-54254. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-54254 in your dependencies?
O3 detects CVE-2026-54254 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.