<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 22:34:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-369681</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-369681</link>
      <description>EUVD-2026-369681</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-369681</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54254</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54254</link>
      <description>&lt;p&gt;Cyberdrop-DL is a bulk asynchronous downloader for multiple file hosts. From 8.5.0 until 9.14.0, the Pixeldrain crawler uses substring host matching instead of requiring the input host to be an exact member of SUPPORTED_DOMAINS, and then reuses that input host for API requests. When a Pixeldrain API key is configured, processing a crafted URL from an attacker-controlled lookalike host causes cyberdrop_dl/crawlers/pixeldrain.py to send the Authorization header to that host. The URL may be introduced through a third-party site that can cause downloads for other sites, and the attacker receives the user&amp;#39;s Pixeldrain API key. This issue is fixed in version 9.14.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Cyberdrop-DL is a bulk asynchronous downloader for multiple file hosts. From 8.5.0 until 9.14.0, the Pixeldrain crawler uses substring host matching instead of requiring the input host to be an exact member of SUPPORTED_DOMAINS, and then reuses that input host for API requests. When a Pixeldrain API key is configured, processing a crafted URL from an attacker-controlled lookalike host causes cyberdrop_dl/crawlers/pixeldrain.py to send the Authorization header to that host. The URL may be introduced through a third-party site that can cause downloads for other sites, and the attacker receives the user&amp;#39;s Pixeldrain API key. This issue is fixed in version 9.14.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54254</guid>
    </item>
    <item>
      <title>GHSA-f5pf-q7c7-m3vv — Pixeldrain API key shared with unverified thirdparty sites</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f5pf-q7c7-m3vv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: cyberdrop-dl-patched&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When processing Pixeldrain URLs, `cyberdrop-dl-patched` could send an `Authorization` header that includes the user&amp;#39;s API key to unverified hosts.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Pixeldrain offers several alternative domains in case the user&amp;#39;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.&lt;/p&gt;
&lt;p&gt;`cyberdrop-dl-patched` matches URLs to a crawler based on their host. If the host contains a crawler&amp;#39;s supported host as a sub-string, it will match to that crawler.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s API key to the malicious actor via the `Authorization` header.&lt;/p&gt;
&lt;p&gt;### 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...)&lt;/p&gt;
&lt;p&gt;### 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__.&lt;/p&gt;
&lt;p&gt;### Workarounds
It&amp;#39;s recommended to upgrade `cyberdrop-dl-patched` to version v9.14.0&lt;/p&gt;
&lt;p&gt;Anyone who has used a Pixeldrain API key with `cyberdrop-dl-patched` should consider them compromised and delete them from their Pixeldrain account.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: cyberdrop-dl-patched&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When processing Pixeldrain URLs, `cyberdrop-dl-patched` could send an `Authorization` header that includes the user&amp;#39;s API key to unverified hosts.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Pixeldrain offers several alternative domains in case the user&amp;#39;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.&lt;/p&gt;
&lt;p&gt;`cyberdrop-dl-patched` matches URLs to a crawler based on their host. If the host contains a crawler&amp;#39;s supported host as a sub-string, it will match to that crawler.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s API key to the malicious actor via the `Authorization` header.&lt;/p&gt;
&lt;p&gt;### 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...)&lt;/p&gt;
&lt;p&gt;### 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__.&lt;/p&gt;
&lt;p&gt;### Workarounds
It&amp;#39;s recommended to upgrade `cyberdrop-dl-patched` to version v9.14.0&lt;/p&gt;
&lt;p&gt;Anyone who has used a Pixeldrain API key with `cyberdrop-dl-patched` should consider them compromised and delete them from their Pixeldrain account.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f5pf-q7c7-m3vv</guid>
    </item>
    <item>
      <title>PYSEC-2026-3460 — Pixeldrain API key shared with unverified thirdparty sites</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3460</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: cyberdrop-dl-patched&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When processing Pixeldrain URLs, `cyberdrop-dl-patched` could send an `Authorization` header that includes the user&amp;#39;s API key to unverified hosts.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Pixeldrain offers several alternative domains in case the user&amp;#39;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.&lt;/p&gt;
&lt;p&gt;`cyberdrop-dl-patched` matches URLs to a crawler based on their host. If the host contains a crawler&amp;#39;s supported host as a sub-string, it will match to that crawler.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s API key to the malicious actor via the `Authorization` header.&lt;/p&gt;
&lt;p&gt;### 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...)&lt;/p&gt;
&lt;p&gt;### 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__.&lt;/p&gt;
&lt;p&gt;### Workarounds
It&amp;#39;s recommended to upgrade `cyberdrop-dl-patched` to version v9.14.0&lt;/p&gt;
&lt;p&gt;Anyone who has used a Pixeldrain API key with `cyberdrop-dl-patched` should consider them compromised and delete them from their Pixeldrain account.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: cyberdrop-dl-patched&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When processing Pixeldrain URLs, `cyberdrop-dl-patched` could send an `Authorization` header that includes the user&amp;#39;s API key to unverified hosts.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Pixeldrain offers several alternative domains in case the user&amp;#39;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.&lt;/p&gt;
&lt;p&gt;`cyberdrop-dl-patched` matches URLs to a crawler based on their host. If the host contains a crawler&amp;#39;s supported host as a sub-string, it will match to that crawler.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s API key to the malicious actor via the `Authorization` header.&lt;/p&gt;
&lt;p&gt;### 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...)&lt;/p&gt;
&lt;p&gt;### 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__.&lt;/p&gt;
&lt;p&gt;### Workarounds
It&amp;#39;s recommended to upgrade `cyberdrop-dl-patched` to version v9.14.0&lt;/p&gt;
&lt;p&gt;Anyone who has used a Pixeldrain API key with `cyberdrop-dl-patched` should consider them compromised and delete them from their Pixeldrain account.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3460</guid>
    </item>
  </channel>
</rss>
