<?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://vulnerability.circl.lu</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 08:29:06 +0000</lastBuildDate>
    <item>
      <title>GHSA-6xv5-86q9-7xr8 — SecureJoin: on windows, paths outside of the rootfs could be inadvertently produced</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6xv5-86q9-7xr8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/cyphar/filepath-securejoin&lt;/p&gt;
&lt;p&gt;### Impact
For Windows users of `github.com/cyphar/filepath-securejoin`, until v0.2.4 it was possible for certain rootfs and path combinations (in particular, where a malicious Unix-style `/`-separated unsafe path was used with a Windows-style rootfs path) to result in generated paths that were outside of the provided rootfs.&lt;/p&gt;
&lt;p&gt;It is unclear to what extent this has a practical impact on real users, but given the possible severity of the issue we have released an emergency patch release that resolves this issue.&lt;/p&gt;
&lt;p&gt;Thanks to  @pjbgf for discovering, debugging, and fixing this issue (as well as writing some tests for it).&lt;/p&gt;
&lt;p&gt;### Patches
c121231e1276e11049547bee5ce68d5a2cfe2d9b is the patch fixing this issue. v0.2.4 contains the fix.&lt;/p&gt;
&lt;p&gt;### Workarounds
Users could use `filepath.FromSlash()` on all unsafe paths before passing them to `filepath-securejoin`.&lt;/p&gt;
&lt;p&gt;### References
See #9.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/cyphar/filepath-securejoin&lt;/p&gt;
&lt;p&gt;### Impact
For Windows users of `github.com/cyphar/filepath-securejoin`, until v0.2.4 it was possible for certain rootfs and path combinations (in particular, where a malicious Unix-style `/`-separated unsafe path was used with a Windows-style rootfs path) to result in generated paths that were outside of the provided rootfs.&lt;/p&gt;
&lt;p&gt;It is unclear to what extent this has a practical impact on real users, but given the possible severity of the issue we have released an emergency patch release that resolves this issue.&lt;/p&gt;
&lt;p&gt;Thanks to  @pjbgf for discovering, debugging, and fixing this issue (as well as writing some tests for it).&lt;/p&gt;
&lt;p&gt;### Patches
c121231e1276e11049547bee5ce68d5a2cfe2d9b is the patch fixing this issue. v0.2.4 contains the fix.&lt;/p&gt;
&lt;p&gt;### Workarounds
Users could use `filepath.FromSlash()` on all unsafe paths before passing them to `filepath-securejoin`.&lt;/p&gt;
&lt;p&gt;### References
See #9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-6xv5-86q9-7xr8</guid>
    </item>
  </channel>
</rss>
