<?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>Sat, 24 Oct 2026 20:24:28 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-53058</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-53058</link>
      <description>EUVD-2026-53058</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-53058</guid>
    </item>
    <item>
      <title>fkie_cve-2019-9686</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2019-9686</link>
      <description>&lt;p&gt;pacman before 5.1.3 allows directory traversal when installing a remote package via a specified URL &amp;#34;pacman -U &amp;lt;url&amp;gt;&amp;#34; due to an unsanitized file name received from a Content-Disposition header. pacman renames the downloaded package file to match the name given in this header. However, pacman did not sanitize this name, which may contain slashes, before calling rename(). A malicious server (or a network MitM if downloading over HTTP) can send a Content-Disposition header to make pacman place the file anywhere in the filesystem, potentially leading to arbitrary root code execution. Notably, this bypasses pacman&amp;#39;s package signature checking. This occurs in curl_download_internal in lib/libalpm/dload.c.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pacman before 5.1.3 allows directory traversal when installing a remote package via a specified URL &amp;#34;pacman -U &amp;lt;url&amp;gt;&amp;#34; due to an unsanitized file name received from a Content-Disposition header. pacman renames the downloaded package file to match the name given in this header. However, pacman did not sanitize this name, which may contain slashes, before calling rename(). A malicious server (or a network MitM if downloading over HTTP) can send a Content-Disposition header to make pacman place the file anywhere in the filesystem, potentially leading to arbitrary root code execution. Notably, this bypasses pacman&amp;#39;s package signature checking. This occurs in curl_download_internal in lib/libalpm/dload.c.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2019-9686</guid>
    </item>
    <item>
      <title>GHSA-2fr8-9j8m-w8vx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2fr8-9j8m-w8vx</link>
      <description>&lt;p&gt;pacman before 5.1.3 allows directory traversal when installing a remote package via a specified URL &amp;#34;pacman -U &amp;lt;url&amp;gt;&amp;#34; due to an unsanitized file name received from a Content-Disposition header. pacman renames the downloaded package file to match the name given in this header. However, pacman did not sanitize this name, which may contain slashes, before calling rename(). A malicious server (or a network MitM if downloading over HTTP) can send a Content-Disposition header to make pacman place the file anywhere in the filesystem, potentially leading to arbitrary root code execution. Notably, this bypasses pacman&amp;#39;s package signature checking. This occurs in curl_download_internal in lib/libalpm/dload.c.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pacman before 5.1.3 allows directory traversal when installing a remote package via a specified URL &amp;#34;pacman -U &amp;lt;url&amp;gt;&amp;#34; due to an unsanitized file name received from a Content-Disposition header. pacman renames the downloaded package file to match the name given in this header. However, pacman did not sanitize this name, which may contain slashes, before calling rename(). A malicious server (or a network MitM if downloading over HTTP) can send a Content-Disposition header to make pacman place the file anywhere in the filesystem, potentially leading to arbitrary root code execution. Notably, this bypasses pacman&amp;#39;s package signature checking. This occurs in curl_download_internal in lib/libalpm/dload.c.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2fr8-9j8m-w8vx</guid>
    </item>
    <item>
      <title>gsd-2019-9686</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2019-9686</link>
      <description>gsd-2019-9686</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2019-9686</guid>
    </item>
  </channel>
</rss>
