<?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>Tue, 13 Oct 2026 20:55:27 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-103061</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-103061</link>
      <description>&lt;p&gt;Improper Limitation of a Pathname to a Restricted Directory (&amp;#39;Path Traversal&amp;#39;) vulnerability in gleam-lang gleam allows a malicious package publisher to delete a directory outside the project&amp;#39;s build directory when a developer builds a project.&lt;/p&gt;
&lt;p&gt;A Hex package release&amp;#39;s metadata carries an app field with the release&amp;#39;s OTP application name. Gleam reads this field from the hex.pm release API when it downloads dependencies and uses it as the package&amp;#39;s build directory name without validating it (hex_manifest_package in compiler-cli/src/dependencies.rs, ProjectPaths::build_directory_for_package). When a dependency fails to compile, Gleam deletes that directory with remove_dir_all. hex.pm didn&amp;#39;t restrict the field to a directory name before 2026-10-12, so a publisher could set it to a value such as ../../../../target or an absolute path. When a project depends on such a release directly or transitively and the release fails to compile, gleam build, gleam check, gleam run, gleam test or gleam export deletes the directory the name resolves to. For a pure Gleam package no publisher code runs.&lt;/p&gt;
&lt;p&gt;This issue affects gleam: from 0.32.4 before 1.19.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 gleam-lang gleam allows a malicious package publisher to delete a directory outside the project&amp;#39;s build directory when a developer builds a project.&lt;/p&gt;
&lt;p&gt;A Hex package release&amp;#39;s metadata carries an app field with the release&amp;#39;s OTP application name. Gleam reads this field from the hex.pm release API when it downloads dependencies and uses it as the package&amp;#39;s build directory name without validating it (hex_manifest_package in compiler-cli/src/dependencies.rs, ProjectPaths::build_directory_for_package). When a dependency fails to compile, Gleam deletes that directory with remove_dir_all. hex.pm didn&amp;#39;t restrict the field to a directory name before 2026-10-12, so a publisher could set it to a value such as ../../../../target or an absolute path. When a project depends on such a release directly or transitively and the release fails to compile, gleam build, gleam check, gleam run, gleam test or gleam export deletes the directory the name resolves to. For a pure Gleam package no publisher code runs.&lt;/p&gt;
&lt;p&gt;This issue affects gleam: from 0.32.4 before 1.19.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-103061</guid>
    </item>
  </channel>
</rss>
