<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=8158&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / yt-dlp in Debian 13 / Devuan 6 affected by serious CVE (Score: High)]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=8158</link>
		<description><![CDATA[The most recent posts in yt-dlp in Debian 13 / Devuan 6 affected by serious CVE (Score: High).]]></description>
		<lastBuildDate>Wed, 19 Aug 2026 20:30:51 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: yt-dlp in Debian 13 / Devuan 6 affected by serious CVE (Score: High)]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=65259#p65259</link>
			<description><![CDATA[<p>You can also use <span class="bbc">~/.local/bin</span> to store (or symlink) portable executables if you want to avoid involving root entirely. I think it&#039;s in <span class="bbc">$PATH</span> by default in Devuan, meaning any executable in this folder can be quickly accessed via terminal. However stuff like <strong>lightdm</strong> can change this, so to be sure you can edit <span class="bbc">~/.bashrc</span> - just append this line:</p><div class="codebox"><pre><code>export PATH=&quot;$HOME/.local/bin:$PATH&quot;</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (Calamity)]]></author>
			<pubDate>Wed, 19 Aug 2026 20:30:51 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=65259#p65259</guid>
		</item>
		<item>
			<title><![CDATA[Re: yt-dlp in Debian 13 / Devuan 6 affected by serious CVE (Score: High)]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=65256#p65256</link>
			<description><![CDATA[<p>Yes I won&#039;t use the package anymore and I will instead install the upstream binary, but my concern is more in general, if this is the attitude towards serious CVEs of Debian then maybe I chose the wrong distro (of course it&#039;s not Devuan&#039;s fault as Devuan depends on Debian for most of the packages, but by choosing Devuan I made myself dependent on Debian which I&#039;m starting to be concerned about) because this means I will have to myself keep track of CVEs for all the packages I installed, as apparently I can&#039;t rely on the Debian packagers for that.</p><p>I only came across this CVE by accident, if I hadn&#039;t I would have still continued to use the vulnerable version until Debian eventually decides to make the fix available for trixie.</p>]]></description>
			<author><![CDATA[dummy@example.com (tux_99)]]></author>
			<pubDate>Wed, 19 Aug 2026 19:41:44 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=65256#p65256</guid>
		</item>
		<item>
			<title><![CDATA[Re: yt-dlp in Debian 13 / Devuan 6 affected by serious CVE (Score: High)]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=65255#p65255</link>
			<description><![CDATA[<p>You could just use the upstream <a href="https://github.com/yt-dlp/yt-dlp/releases/latest/download/yt-dlp" rel="nofollow">binary</a> (alternatively, use this <a href="https://github.com/yt-dlp/yt-dlp/releases/latest/download/yt-dlp_linux" rel="nofollow">binary</a> if your Python version is too old or plain C is more appealing to you).</p><p>Download that, move it to your <span class="bbc">/usr/local/bin</span>, and then run <span class="bbc">chmod 744</span> on it so that it can be executed and run as a non-root user. Simply typing <span class="bbc">yt-dlp</span> will point to that upstream binary you downloaded (by default), and when you want to check for updates, just run <span class="bbc">sudo yt-dlp -U</span>.</p>]]></description>
			<author><![CDATA[dummy@example.com (brocashelm)]]></author>
			<pubDate>Wed, 19 Aug 2026 19:26:22 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=65255#p65255</guid>
		</item>
		<item>
			<title><![CDATA[yt-dlp in Debian 13 / Devuan 6 affected by serious CVE (Score: High)]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=65254#p65254</link>
			<description><![CDATA[<div class="quotebox"><blockquote><div><p>Prior to 2026.7.4, the --write-link, --write-url-link, and --write-desktop-link options can write .url or .desktop shortcut files using attacker-controlled webpage_url or filename metadata without sufficient validation or escaping, allowing malicious file:// URI injection on Windows or <strong>newline-based desktop entry key injection on Linux that can execute commands if the generated shortcut is opened</strong>. This issue is fixed in version 2026.7.4.</p></div></blockquote></div><p><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-55404" rel="nofollow">https://nvd.nist.gov/vuln/detail/CVE-2026-55404</a></p><p>Debian 13/Devuan 6 still has an old version from 2025 in the main stable repo and 2026.03.17 in backports, so a month after the publication of the CVE there is still no sign in the repos of the 2026.7.4 version that fixes this bug.</p><p>Being new to the Debian/Devuan world I&#039;m a bit concerned about this apparent lackadaisical attitude by some Debian packagers in the face of a serious vulnerability. Other distros such as Arch have provided the fixed version within 24 hours of the upstream release.</p><p>Edit:<br />I see Debian has 2026.7.4 packaged up in forky and sid, what are they waiting for to release it also as a security update for trixie?<br /><a href="https://packages.debian.org/sid/yt-dlp" rel="nofollow">https://packages.debian.org/sid/yt-dlp</a></p>]]></description>
			<author><![CDATA[dummy@example.com (tux_99)]]></author>
			<pubDate>Wed, 19 Aug 2026 19:13:22 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=65254#p65254</guid>
		</item>
	</channel>
</rss>
