<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-13T08:17:52.334237+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-30915</id>
    <title>fkie_cve-2026-30915</title>
    <updated>2026-11-13T08:17:52.336279+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>SFTPGo is an open source, event-driven file transfer solution. SFTPGo versions before v2.7.1 contain an input validation issue in the handling of dynamic group paths, for example, home directories or key prefixes. When a group is configured with a dynamic home directory or key prefix using placeholders like %username%, the value replacing the placeholder is not strictly sanitized against relative path components. Consequently, if a user is created with a specially crafted username the resulting path may resolve to a parent directory instead of the intended sub-directory. This issue is fixed in version v2.7.1</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-30915"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-m83q-5wr4-4gfp</id>
    <title>GHSA-m83q-5wr4-4gfp — SFTPGo improperly sanitizes placeholders in group home directories/key prefixes</title>
    <updated>2026-11-13T08:17:52.336363+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/drakkan/sftpgo/v2</p>
<p>### Impact</p>
<p>SFTPGo versions before v2.7.1 contain an input validation issue in the handling of dynamic group paths, for example, home directories or key prefixes.</p>
<p>When a group is configured with a dynamic home directory or key prefix using placeholders like `%username%`, the value replacing the placeholder is not strictly sanitized against relative path components. Consequently, if a user is created with a specially crafted username the resulting path may resolve to a parent directory instead of the intended sub-directory.</p>
<p>### Patches</p>
<p>This issue is fixed in version v2.7.1</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-m83q-5wr4-4gfp"/>
  </entry>
</feed>
