<?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://db.gcve.eu</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>Thu, 01 Oct 2026 05:51:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-50019 — yt-dlp: File Downloader cookie leak with curl</title>
      <link>https://db.gcve.eu/vuln/cve-2026-50019</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; yt-dlp&lt;/p&gt;
&lt;p&gt;yt-dlp is a command-line audio/video downloader. From 2023.09.24 until 2026.06.09, if curl is used as an external downloader for yt-dlp, cookies may be leaked to an unintended host upon HTTP redirect or when the host for download fragments differs from their parent manifest&amp;#39;s. At the file download stage, the cookies are passed by yt-dlp to the file downloader via --cookie. However, unless these are loaded from a file, this operation does not activate the cookie engine. As a result, curl will send cookies with requests to domains or paths for which the cookies are not scoped. This vulnerability is fixed in 2026.06.09.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; yt-dlp&lt;/p&gt;
&lt;p&gt;yt-dlp is a command-line audio/video downloader. From 2023.09.24 until 2026.06.09, if curl is used as an external downloader for yt-dlp, cookies may be leaked to an unintended host upon HTTP redirect or when the host for download fragments differs from their parent manifest&amp;#39;s. At the file download stage, the cookies are passed by yt-dlp to the file downloader via --cookie. However, unless these are loaded from a file, this operation does not activate the cookie engine. As a result, curl will send cookies with requests to domains or paths for which the cookies are not scoped. This vulnerability is fixed in 2026.06.09.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-50019</guid>
    </item>
    <item>
      <title>GHSA-f7j3-774f-rfhj — yt-dlp: File Downloader cookie leak with curl</title>
      <link>https://db.gcve.eu/vuln/ghsa-f7j3-774f-rfhj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: yt-dlp&lt;/p&gt;
&lt;p&gt;### Summary
If curl is used an external downloader for yt-dlp, cookies may be leaked to an unintended host upon HTTP redirect or when the host for download fragments differs from their parent manifest&amp;#39;s.&lt;/p&gt;
&lt;p&gt;This is the equivalent to [GHSA-v8mc-9377-rwjj](&amp;lt;https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-v8mc-9377-rwjj&amp;gt;) for the `curl` downloader. The vulnerable behavior is present in [yt-dlp](https://github.com/yt-dlp/yt-dlp) released since 2023.09.24.&lt;/p&gt;
&lt;p&gt;### Details
At the file download stage, the cookies are passed by yt-dlp to the file downloader via `--cookie`. However, unless these are loaded from a file, this operation does not activate the cookie engine. As a result, `curl` will send cookies with requests to domains or paths for which the cookies are not scoped.&lt;/p&gt;
&lt;p&gt;An example of a potential attack scenario exploiting this vulnerability:
1. an attacker has crafted a malicious website with an embedded URL designed to be detected by yt-dlp as a video download. This embedded URL has the domain of a trusted site that the user has loaded cookies for, and conducts an [unvalidated redirect](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html) to a target URL.
2. yt-dlp extracts this URL and calculates the cookies which are then passed to `curl`.
3. the download URL redirects to a server controlled by the attacker, to which `curl` forwards the user&amp;#39;s sensitive cookie information.&lt;/p&gt;
&lt;p&gt;### Patches
yt-dlp version 2026.06.09 fixes thi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: yt-dlp&lt;/p&gt;
&lt;p&gt;### Summary
If curl is used an external downloader for yt-dlp, cookies may be leaked to an unintended host upon HTTP redirect or when the host for download fragments differs from their parent manifest&amp;#39;s.&lt;/p&gt;
&lt;p&gt;This is the equivalent to [GHSA-v8mc-9377-rwjj](&amp;lt;https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-v8mc-9377-rwjj&amp;gt;) for the `curl` downloader. The vulnerable behavior is present in [yt-dlp](https://github.com/yt-dlp/yt-dlp) released since 2023.09.24.&lt;/p&gt;
&lt;p&gt;### Details
At the file download stage, the cookies are passed by yt-dlp to the file downloader via `--cookie`. However, unless these are loaded from a file, this operation does not activate the cookie engine. As a result, `curl` will send cookies with requests to domains or paths for which the cookies are not scoped.&lt;/p&gt;
&lt;p&gt;An example of a potential attack scenario exploiting this vulnerability:
1. an attacker has crafted a malicious website with an embedded URL designed to be detected by yt-dlp as a video download. This embedded URL has the domain of a trusted site that the user has loaded cookies for, and conducts an [unvalidated redirect](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html) to a target URL.
2. yt-dlp extracts this URL and calculates the cookies which are then passed to `curl`.
3. the download URL redirects to a server controlled by the attacker, to which `curl` forwards the user&amp;#39;s sensitive cookie information.&lt;/p&gt;
&lt;p&gt;### Patches
yt-dlp version 2026.06.09 fixes thi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-f7j3-774f-rfhj</guid>
    </item>
    <item>
      <title>PYSEC-2026-3431 — yt-dlp: File Downloader cookie leak with curl</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-3431</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: yt-dlp&lt;/p&gt;
&lt;p&gt;### Summary
If curl is used an external downloader for yt-dlp, cookies may be leaked to an unintended host upon HTTP redirect or when the host for download fragments differs from their parent manifest&amp;#39;s.&lt;/p&gt;
&lt;p&gt;This is the equivalent to [GHSA-v8mc-9377-rwjj](&amp;lt;https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-v8mc-9377-rwjj&amp;gt;) for the `curl` downloader. The vulnerable behavior is present in [yt-dlp](https://github.com/yt-dlp/yt-dlp) released since 2023.09.24.&lt;/p&gt;
&lt;p&gt;### Details
At the file download stage, the cookies are passed by yt-dlp to the file downloader via `--cookie`. However, unless these are loaded from a file, this operation does not activate the cookie engine. As a result, `curl` will send cookies with requests to domains or paths for which the cookies are not scoped.&lt;/p&gt;
&lt;p&gt;An example of a potential attack scenario exploiting this vulnerability:
1. an attacker has crafted a malicious website with an embedded URL designed to be detected by yt-dlp as a video download. This embedded URL has the domain of a trusted site that the user has loaded cookies for, and conducts an [unvalidated redirect](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html) to a target URL.
2. yt-dlp extracts this URL and calculates the cookies which are then passed to `curl`.
3. the download URL redirects to a server controlled by the attacker, to which `curl` forwards the user&amp;#39;s sensitive cookie information.&lt;/p&gt;
&lt;p&gt;### Patches
yt-dlp version 2026.06.09 fixes thi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: yt-dlp&lt;/p&gt;
&lt;p&gt;### Summary
If curl is used an external downloader for yt-dlp, cookies may be leaked to an unintended host upon HTTP redirect or when the host for download fragments differs from their parent manifest&amp;#39;s.&lt;/p&gt;
&lt;p&gt;This is the equivalent to [GHSA-v8mc-9377-rwjj](&amp;lt;https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-v8mc-9377-rwjj&amp;gt;) for the `curl` downloader. The vulnerable behavior is present in [yt-dlp](https://github.com/yt-dlp/yt-dlp) released since 2023.09.24.&lt;/p&gt;
&lt;p&gt;### Details
At the file download stage, the cookies are passed by yt-dlp to the file downloader via `--cookie`. However, unless these are loaded from a file, this operation does not activate the cookie engine. As a result, `curl` will send cookies with requests to domains or paths for which the cookies are not scoped.&lt;/p&gt;
&lt;p&gt;An example of a potential attack scenario exploiting this vulnerability:
1. an attacker has crafted a malicious website with an embedded URL designed to be detected by yt-dlp as a video download. This embedded URL has the domain of a trusted site that the user has loaded cookies for, and conducts an [unvalidated redirect](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html) to a target URL.
2. yt-dlp extracts this URL and calculates the cookies which are then passed to `curl`.
3. the download URL redirects to a server controlled by the attacker, to which `curl` forwards the user&amp;#39;s sensitive cookie information.&lt;/p&gt;
&lt;p&gt;### Patches
yt-dlp version 2026.06.09 fixes thi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-3431</guid>
    </item>
  </channel>
</rss>
