<?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>Fri, 02 Oct 2026 22:47:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-32108 — Copyparty ftp/sftp: Sharing a single file did not fully restrict source-folder access</title>
      <link>https://db.gcve.eu/vuln/cve-2026-32108</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 9001 copyparty&lt;/p&gt;
&lt;p&gt;Copyparty is a portable file server. Prior to 1.20.12, there was a missing permission-check in the shares feature (the shr global-option). This vulnerability only applies when the shares feature is used for the specific purpose of creating a share of just a single file inside a folder or either the FTP or SFTP server is enabled, and also made publicly accessible. Given these conditions, when a user is browsing a share through either FTP or SFTP (not http or https), they can gain read-access to the remaining files inside the shared folder by guessing/bruteforcing the filenames. It was not possible to descend into subdirectories in this manner; only the sibling files were accessible. This vulnerability is similar to CVE-2025-58753 which was previously fixed for HTTP and HTTPS, but not for FTP. The FTPS server did not yet exist at that time. This vulnerability is fixed in 1.20.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 9001 copyparty&lt;/p&gt;
&lt;p&gt;Copyparty is a portable file server. Prior to 1.20.12, there was a missing permission-check in the shares feature (the shr global-option). This vulnerability only applies when the shares feature is used for the specific purpose of creating a share of just a single file inside a folder or either the FTP or SFTP server is enabled, and also made publicly accessible. Given these conditions, when a user is browsing a share through either FTP or SFTP (not http or https), they can gain read-access to the remaining files inside the shared folder by guessing/bruteforcing the filenames. It was not possible to descend into subdirectories in this manner; only the sibling files were accessible. This vulnerability is similar to CVE-2025-58753 which was previously fixed for HTTP and HTTPS, but not for FTP. The FTPS server did not yet exist at that time. This vulnerability is fixed in 1.20.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-32108</guid>
    </item>
    <item>
      <title>GHSA-67rw-2x62-mqqm — Copyparty ftp/sftp: Sharing a single file did not fully restrict source-folder access</title>
      <link>https://db.gcve.eu/vuln/ghsa-67rw-2x62-mqqm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: copyparty&lt;/p&gt;
&lt;p&gt;There was a missing permission-check in the shares feature (the `shr` global-option).&lt;/p&gt;
&lt;p&gt;This vulnerability only applies in the following scenario:
* The [shares](https://github.com/9001/copyparty/#shares) feature is used for the specific purpose of creating a share of just a single file inside a folder
* Either the FTP or SFTP server is enabled, and also made publically accessible
  * If a share is password-protected, then SFTP was not vulnerable unless the `sftp-pw` global-option was also enabled&lt;/p&gt;
&lt;p&gt;Given these conditions, when a user is browsing a share through either FTP or SFTP (not http or https), they can gain read-access to the remaining files inside the shared folder by guessing/bruteforcing the filenames.&lt;/p&gt;
&lt;p&gt;It was not possible to descend into subdirectories in this manner; only the sibling files were accessible.&lt;/p&gt;
&lt;p&gt;This issue did not affect filekeys or dirkeys.&lt;/p&gt;
&lt;p&gt;This vulnerability is [CVE-2025-58753](https://nvd.nist.gov/vuln/detail/CVE-2025-58753) which was previously fixed for HTTP and HTTPS, but not for FTP. The FTPS server did not yet exist at that time.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: copyparty&lt;/p&gt;
&lt;p&gt;There was a missing permission-check in the shares feature (the `shr` global-option).&lt;/p&gt;
&lt;p&gt;This vulnerability only applies in the following scenario:
* The [shares](https://github.com/9001/copyparty/#shares) feature is used for the specific purpose of creating a share of just a single file inside a folder
* Either the FTP or SFTP server is enabled, and also made publically accessible
  * If a share is password-protected, then SFTP was not vulnerable unless the `sftp-pw` global-option was also enabled&lt;/p&gt;
&lt;p&gt;Given these conditions, when a user is browsing a share through either FTP or SFTP (not http or https), they can gain read-access to the remaining files inside the shared folder by guessing/bruteforcing the filenames.&lt;/p&gt;
&lt;p&gt;It was not possible to descend into subdirectories in this manner; only the sibling files were accessible.&lt;/p&gt;
&lt;p&gt;This issue did not affect filekeys or dirkeys.&lt;/p&gt;
&lt;p&gt;This vulnerability is [CVE-2025-58753](https://nvd.nist.gov/vuln/detail/CVE-2025-58753) which was previously fixed for HTTP and HTTPS, but not for FTP. The FTPS server did not yet exist at that time.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-67rw-2x62-mqqm</guid>
    </item>
    <item>
      <title>PYSEC-2026-31</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-31</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: copyparty&lt;/p&gt;
&lt;p&gt;Copyparty is a portable file server. Prior to 1.20.12, there was a missing permission-check in the shares feature (the shr global-option). This vulnerability only applies when the shares feature is used for the specific purpose of creating a share of just a single file inside a folder or either the FTP or SFTP server is enabled, and also made publicly accessible. Given these conditions, when a user is browsing a share through either FTP or SFTP (not http or https), they can gain read-access to the remaining files inside the shared folder by guessing/bruteforcing the filenames. It was not possible to descend into subdirectories in this manner; only the sibling files were accessible. This vulnerability is similar to CVE-2025-58753 which was previously fixed for HTTP and HTTPS, but not for FTP. The FTPS server did not yet exist at that time. This vulnerability is fixed in 1.20.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: copyparty&lt;/p&gt;
&lt;p&gt;Copyparty is a portable file server. Prior to 1.20.12, there was a missing permission-check in the shares feature (the shr global-option). This vulnerability only applies when the shares feature is used for the specific purpose of creating a share of just a single file inside a folder or either the FTP or SFTP server is enabled, and also made publicly accessible. Given these conditions, when a user is browsing a share through either FTP or SFTP (not http or https), they can gain read-access to the remaining files inside the shared folder by guessing/bruteforcing the filenames. It was not possible to descend into subdirectories in this manner; only the sibling files were accessible. This vulnerability is similar to CVE-2025-58753 which was previously fixed for HTTP and HTTPS, but not for FTP. The FTPS server did not yet exist at that time. This vulnerability is fixed in 1.20.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-31</guid>
    </item>
  </channel>
</rss>
