<?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>Wed, 14 Oct 2026 14:43:38 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-96612</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-96612</link>
      <description>&lt;p&gt;Improper Limitation of a Pathname to a Restricted Directory (&amp;#39;Path Traversal&amp;#39;) vulnerability in hexpm hex allows a malicious package publisher to delete a directory outside the project&amp;#39;s deps directory and extract package files into it when a developer fetches dependencies.&lt;/p&gt;
&lt;p&gt;A package release&amp;#39;s requirements carry an app label that names the dependency&amp;#39;s OTP application. Hex takes this label from the repository&amp;#39;s signed registry and uses it as the dependency&amp;#39;s application name without validating it (Hex.RemoteConverger.deps/2, Hex.Mix.to_lock/1). Mix derives the dependency&amp;#39;s checkout directory as deps/&amp;lt;app&amp;gt;, and Hex.SCM.update/1 runs File.rm_rf!/1 on that directory and unpacks the package into it. hex.pm only checks the label&amp;#39;s length, so a publisher can set it to a value such as ../../target. When a project depends on such a release directly or transitively, mix deps.get or mix deps.update deletes the directory the label resolves to and writes the labelled package&amp;#39;s files there. This happens before any dependency code is compiled.&lt;/p&gt;
&lt;p&gt;This issue affects hex: from 0.6.0 before 2.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Limitation of a Pathname to a Restricted Directory (&amp;#39;Path Traversal&amp;#39;) vulnerability in hexpm hex allows a malicious package publisher to delete a directory outside the project&amp;#39;s deps directory and extract package files into it when a developer fetches dependencies.&lt;/p&gt;
&lt;p&gt;A package release&amp;#39;s requirements carry an app label that names the dependency&amp;#39;s OTP application. Hex takes this label from the repository&amp;#39;s signed registry and uses it as the dependency&amp;#39;s application name without validating it (Hex.RemoteConverger.deps/2, Hex.Mix.to_lock/1). Mix derives the dependency&amp;#39;s checkout directory as deps/&amp;lt;app&amp;gt;, and Hex.SCM.update/1 runs File.rm_rf!/1 on that directory and unpacks the package into it. hex.pm only checks the label&amp;#39;s length, so a publisher can set it to a value such as ../../target. When a project depends on such a release directly or transitively, mix deps.get or mix deps.update deletes the directory the label resolves to and writes the labelled package&amp;#39;s files there. This happens before any dependency code is compiled.&lt;/p&gt;
&lt;p&gt;This issue affects hex: from 0.6.0 before 2.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-96612</guid>
    </item>
  </channel>
</rss>
