<?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>Mon, 05 Oct 2026 12:50:29 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-364392</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364392</link>
      <description>EUVD-2026-364392</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364392</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42795</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42795</link>
      <description>&lt;p&gt;Symlink following vulnerability in Gleam&amp;#39;s Hex package export allows files outside the project root to be embedded in the generated package tarball.&lt;/p&gt;
&lt;p&gt;The file collection helpers (gleam_files, native_files, private_files) in compiler-cli/src/fs.rs use follow_links(true) when walking publishable directories such as src/ and priv/. The collected paths are added to the package archive via add_path_to_tar in compiler-cli/src/publish.rs without verifying that the resolved target remains within the project root. A symlink placed under a publishable directory will cause gleam export hex-tarball or gleam publish to embed the contents of the symlink target into the generated Hex package.&lt;/p&gt;
&lt;p&gt;An attacker with write access to the project repository can place a symlink in src/ or priv/ pointing to an arbitrary file. When a maintainer or CI pipeline runs gleam publish or gleam export hex-tarball, local files readable by the publisher (such as secrets, tokens, or SSH keys) are silently embedded into the published package artifact.&lt;/p&gt;
&lt;p&gt;This issue affects Gleam from 0.10.0-rc1 until 1.17.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Symlink following vulnerability in Gleam&amp;#39;s Hex package export allows files outside the project root to be embedded in the generated package tarball.&lt;/p&gt;
&lt;p&gt;The file collection helpers (gleam_files, native_files, private_files) in compiler-cli/src/fs.rs use follow_links(true) when walking publishable directories such as src/ and priv/. The collected paths are added to the package archive via add_path_to_tar in compiler-cli/src/publish.rs without verifying that the resolved target remains within the project root. A symlink placed under a publishable directory will cause gleam export hex-tarball or gleam publish to embed the contents of the symlink target into the generated Hex package.&lt;/p&gt;
&lt;p&gt;An attacker with write access to the project repository can place a symlink in src/ or priv/ pointing to an arbitrary file. When a maintainer or CI pipeline runs gleam publish or gleam export hex-tarball, local files readable by the publisher (such as secrets, tokens, or SSH keys) are silently embedded into the published package artifact.&lt;/p&gt;
&lt;p&gt;This issue affects Gleam from 0.10.0-rc1 until 1.17.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42795</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10953-1 — gleam-1.17.0-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10953-1</link>
      <description>&lt;p&gt;gleam-1.17.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;gleam-1.17.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10953-1</guid>
    </item>
  </channel>
</rss>
