<?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>Thu, 05 Nov 2026 14:24:10 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-104102</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-104102</link>
      <description>&lt;p&gt;copyparty is a portable file server. Prior to 1.20.19, FTP upload path handling does not confine destinations to configured copyparty volumes. When FTP or FTPS is explicitly enabled, a low-privileged authenticated user can submit traversal paths during upload to create a new file outside configured volumes wherever the copyparty process has write permission. The attacker cannot read or overwrite files, the output name receives a randomized suffix, and copyparty does not execute the file; however, unrelated software on the same host could process the newly created file. This issue is fixed in version 1.20.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;copyparty is a portable file server. Prior to 1.20.19, FTP upload path handling does not confine destinations to configured copyparty volumes. When FTP or FTPS is explicitly enabled, a low-privileged authenticated user can submit traversal paths during upload to create a new file outside configured volumes wherever the copyparty process has write permission. The attacker cannot read or overwrite files, the output name receives a randomized suffix, and copyparty does not execute the file; however, unrelated software on the same host could process the newly created file. This issue is fixed in version 1.20.19.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-104102</guid>
    </item>
    <item>
      <title>GHSA-phv8-wgjp-g4p9 — copyparty FTP: upload outside defined volumes (limited path traversal)</title>
      <link>https://db.gcve.eu/vuln/ghsa-phv8-wgjp-g4p9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: copyparty&lt;/p&gt;
&lt;p&gt;The FTP and FTPS server -- if enabled -- would allow uploading to any folder that the copyparty process had permission to write to.&lt;/p&gt;
&lt;p&gt;The FTP-server is default-disabled, and must be explicitly enabled in the config with global-option `ftp` or `ftps` to be affected. Additionally, SFTP was not affected at all; only FTP and FTPS.&lt;/p&gt;
&lt;p&gt;This was not a full read/write path-traversal; it had the following limitations:
* Only applied to uploads; it was not possible to read/download existing files in this manner.
* The output filename was not fully controllable; a randomized suffix would always be appended to the filename.
* Existing files could not be overwritten or appended to; only new files could be created.
* Filesystem-permissions would prevent writing to system folders, as copyparty surely does not run as root in most deployments.
* Copyparty itself will not execute arbitrary files as code by default, so this vulnerability could not be used to execute arbitrary code through copyparty.&lt;/p&gt;
&lt;p&gt;The main concern is the potential effect on other unrelated software which is running on the same system.&lt;/p&gt;
&lt;p&gt;The severity is assuming the worst case (SC:H/SI:H), that the same machine is running some unrelated software that will execute new arbitrarily-named files as code, and that the copyparty process has sufficient privileges to write files into the config-folder of that unrelated software.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: copyparty&lt;/p&gt;
&lt;p&gt;The FTP and FTPS server -- if enabled -- would allow uploading to any folder that the copyparty process had permission to write to.&lt;/p&gt;
&lt;p&gt;The FTP-server is default-disabled, and must be explicitly enabled in the config with global-option `ftp` or `ftps` to be affected. Additionally, SFTP was not affected at all; only FTP and FTPS.&lt;/p&gt;
&lt;p&gt;This was not a full read/write path-traversal; it had the following limitations:
* Only applied to uploads; it was not possible to read/download existing files in this manner.
* The output filename was not fully controllable; a randomized suffix would always be appended to the filename.
* Existing files could not be overwritten or appended to; only new files could be created.
* Filesystem-permissions would prevent writing to system folders, as copyparty surely does not run as root in most deployments.
* Copyparty itself will not execute arbitrary files as code by default, so this vulnerability could not be used to execute arbitrary code through copyparty.&lt;/p&gt;
&lt;p&gt;The main concern is the potential effect on other unrelated software which is running on the same system.&lt;/p&gt;
&lt;p&gt;The severity is assuming the worst case (SC:H/SI:H), that the same machine is running some unrelated software that will execute new arbitrarily-named files as code, and that the copyparty process has sufficient privileges to write files into the config-folder of that unrelated software.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-phv8-wgjp-g4p9</guid>
    </item>
  </channel>
</rss>
