<?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 23:08:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-266979</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-266979</link>
      <description>EUVD-2026-266979</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-266979</guid>
    </item>
    <item>
      <title>fkie_cve-2026-24846</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-24846</link>
      <description>&lt;p&gt;malcontent discovers supply-chain compromises through. context, differential analysis, and YARA. Starting in version 1.8.0 and prior to version 1.20.3, malcontent could be made to create symlinks outside the intended extraction directory when scanning a specially crafted tar or deb archive. The `handleSymlink` function received arguments in the wrong order, causing the symlink target to be used as the symlink location. Additionally, symlink targets were not validated to ensure they resolved within the extraction directory. Version 1.20.3 introduces fixes that swap handleSymlink arguments, validate symlink location, and validate symlink targets that resolve within an extraction directory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;malcontent discovers supply-chain compromises through. context, differential analysis, and YARA. Starting in version 1.8.0 and prior to version 1.20.3, malcontent could be made to create symlinks outside the intended extraction directory when scanning a specially crafted tar or deb archive. The `handleSymlink` function received arguments in the wrong order, causing the symlink target to be used as the symlink location. Additionally, symlink targets were not validated to ensure they resolved within the extraction directory. Version 1.20.3 introduces fixes that swap handleSymlink arguments, validate symlink location, and validate symlink targets that resolve within an extraction directory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-24846</guid>
    </item>
    <item>
      <title>GHSA-923j-vrcg-hxwh — malcontent vulnerable to symlink Path Traversal via handleSymlink argument confusion in archive extraction</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-923j-vrcg-hxwh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/chainguard-dev/malcontent&lt;/p&gt;
&lt;p&gt;malcontent could be made to create symlinks outside the intended extraction directory when scanning a specially crafted tar or deb archive. The `handleSymlink` function received arguments in the wrong order, causing the symlink target to be used as the symlink location. Additionally, symlink targets were not validated to ensure they resolved within the extraction directory.&lt;/p&gt;
&lt;p&gt;**Fixes:**
- [Swap handleSymlink arguments; validate symlink location](https://github.com/chainguard-dev/malcontent/commit/a7dd8a5328ddbaf235568437813efa7591e00017)
- [Validate symlink targets resolve within extraction directory](https://github.com/chainguard-dev/malcontent/commit/259fca5abc004f3ab238895463ef280a87f30e96)&lt;/p&gt;
&lt;p&gt;**Acknowledgements**&lt;/p&gt;
&lt;p&gt;Thank you to Oleh Konko from [1seal](https://1seal.org/) for discovering and reporting this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/chainguard-dev/malcontent&lt;/p&gt;
&lt;p&gt;malcontent could be made to create symlinks outside the intended extraction directory when scanning a specially crafted tar or deb archive. The `handleSymlink` function received arguments in the wrong order, causing the symlink target to be used as the symlink location. Additionally, symlink targets were not validated to ensure they resolved within the extraction directory.&lt;/p&gt;
&lt;p&gt;**Fixes:**
- [Swap handleSymlink arguments; validate symlink location](https://github.com/chainguard-dev/malcontent/commit/a7dd8a5328ddbaf235568437813efa7591e00017)
- [Validate symlink targets resolve within extraction directory](https://github.com/chainguard-dev/malcontent/commit/259fca5abc004f3ab238895463ef280a87f30e96)&lt;/p&gt;
&lt;p&gt;**Acknowledgements**&lt;/p&gt;
&lt;p&gt;Thank you to Oleh Konko from [1seal](https://1seal.org/) for discovering and reporting this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-923j-vrcg-hxwh</guid>
    </item>
  </channel>
</rss>
