<?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>Thu, 08 Oct 2026 17:15:36 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-71415</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-71415</link>
      <description>&lt;p&gt;Kirby is an open-source content management system. From 5.0.0 until 5.5.2, Kirby&amp;#39;s REST API chunk upload handler in src/Api/Upload.php did not run the relevant upload authorization preflight in Kirby\Api\Upload::process() before Kirby\Api\Upload::processChunk() persisted chunk data. An authenticated user with the access.panel permission enabled but with files.create, files.replace, and user/users.update permissions disabled could submit requests with an Upload-Length header and leave unfinished chunks in site/cache/.uploads for 24 hours. Repeating this process could consume attacker-controlled temporary storage, prevent other users from uploading files, or prevent site logic from storing data, although final permission checks still prevented unauthorized files from reaching the content or site/accounts directories. This issue is fixed in version 5.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kirby is an open-source content management system. From 5.0.0 until 5.5.2, Kirby&amp;#39;s REST API chunk upload handler in src/Api/Upload.php did not run the relevant upload authorization preflight in Kirby\Api\Upload::process() before Kirby\Api\Upload::processChunk() persisted chunk data. An authenticated user with the access.panel permission enabled but with files.create, files.replace, and user/users.update permissions disabled could submit requests with an Upload-Length header and leave unfinished chunks in site/cache/.uploads for 24 hours. Repeating this process could consume attacker-controlled temporary storage, prevent other users from uploading files, or prevent site logic from storing data, although final permission checks still prevented unauthorized files from reaching the content or site/accounts directories. This issue is fixed in version 5.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-71415</guid>
    </item>
    <item>
      <title>GHSA-67mx-6wf2-92xp — Kirby: File upload permissions are not checked during processing of chunk data</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-67mx-6wf2-92xp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: getkirby/cms&lt;/p&gt;
&lt;p&gt;### TL;DR&lt;/p&gt;
&lt;p&gt;This vulnerability affects all Kirby sites where users of a particular role have access to the REST API (`access.panel` permission is enabled) but no permission to upload any kind of file (`files.create`, `files.replace` and `user/users.update` permissions are all disabled).&lt;/p&gt;
&lt;p&gt;It was possible to fill up the temporary directory for chunked uploads with unfinished chunks even as a user without any upload permission.&lt;/p&gt;
&lt;p&gt;**This vulnerability is of high severity for affected sites.**&lt;/p&gt;
&lt;p&gt;Your Kirby sites are *not* affected if you intend all users of your site to be able to upload files. The vulnerability can only be exploited by authenticated users. It was *not* possible to bypass the actual permission checks for any files that end up in the `content` or `site/accounts` folders.&lt;/p&gt;
&lt;p&gt;----&lt;/p&gt;
&lt;p&gt;### Introduction&lt;/p&gt;
&lt;p&gt;Missing authorization allows authenticated users to perform actions they are not intended to have access to.&lt;/p&gt;
&lt;p&gt;The effects of missing authorization can include unauthorized access to sensitive information as well as unauthorized changes to content or system information.&lt;/p&gt;
&lt;p&gt;### Affected components&lt;/p&gt;
&lt;p&gt;Kirby&amp;#39;s REST API provides routes to upload files, specifically to create content files, replace existing content files and to create and replace user avatars.&lt;/p&gt;
&lt;p&gt;Each upload route takes either full file upload requests or chunked upload requests that can be continued in subsequent requests.
During a chunked upload, the incomplete state of the uploaded file is stored in a temporary direct…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: getkirby/cms&lt;/p&gt;
&lt;p&gt;### TL;DR&lt;/p&gt;
&lt;p&gt;This vulnerability affects all Kirby sites where users of a particular role have access to the REST API (`access.panel` permission is enabled) but no permission to upload any kind of file (`files.create`, `files.replace` and `user/users.update` permissions are all disabled).&lt;/p&gt;
&lt;p&gt;It was possible to fill up the temporary directory for chunked uploads with unfinished chunks even as a user without any upload permission.&lt;/p&gt;
&lt;p&gt;**This vulnerability is of high severity for affected sites.**&lt;/p&gt;
&lt;p&gt;Your Kirby sites are *not* affected if you intend all users of your site to be able to upload files. The vulnerability can only be exploited by authenticated users. It was *not* possible to bypass the actual permission checks for any files that end up in the `content` or `site/accounts` folders.&lt;/p&gt;
&lt;p&gt;----&lt;/p&gt;
&lt;p&gt;### Introduction&lt;/p&gt;
&lt;p&gt;Missing authorization allows authenticated users to perform actions they are not intended to have access to.&lt;/p&gt;
&lt;p&gt;The effects of missing authorization can include unauthorized access to sensitive information as well as unauthorized changes to content or system information.&lt;/p&gt;
&lt;p&gt;### Affected components&lt;/p&gt;
&lt;p&gt;Kirby&amp;#39;s REST API provides routes to upload files, specifically to create content files, replace existing content files and to create and replace user avatars.&lt;/p&gt;
&lt;p&gt;Each upload route takes either full file upload requests or chunked upload requests that can be continued in subsequent requests.
During a chunked upload, the incomplete state of the uploaded file is stored in a temporary direct…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-67mx-6wf2-92xp</guid>
    </item>
  </channel>
</rss>
