<?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 10:15:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-75594</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-75594</link>
      <description>&lt;p&gt;Kirby is an open-source content management system. Prior to 4.9.5 and 5.5.2, depending on the release line, Kirby&amp;#39;s media handler in src/Cms/Media.php allowed Kirby\Cms\Media::thumb() to append a path-bearing filename to a validated parent media directory. On nginx, PHP&amp;#39;s built-in server, or Apache with AllowEncodedSlashes enabled, a remote attacker could submit encoded slash characters such as %2f in the filename and traverse outside the parent&amp;#39;s media directory. Differences between responses for existing and nonexistent thumbnail configurations disclosed whether an arbitrary .json file existed, and a .json file containing a valid filename key could cause the referenced image to be returned and the job file to be deleted. The related file::version path in src/Filesystem/Asset.php also accepted ../ sequences outside the intended index root. This issue is fixed in versions 4.9.5 and 5.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kirby is an open-source content management system. Prior to 4.9.5 and 5.5.2, depending on the release line, Kirby&amp;#39;s media handler in src/Cms/Media.php allowed Kirby\Cms\Media::thumb() to append a path-bearing filename to a validated parent media directory. On nginx, PHP&amp;#39;s built-in server, or Apache with AllowEncodedSlashes enabled, a remote attacker could submit encoded slash characters such as %2f in the filename and traverse outside the parent&amp;#39;s media directory. Differences between responses for existing and nonexistent thumbnail configurations disclosed whether an arbitrary .json file existed, and a .json file containing a valid filename key could cause the referenced image to be returned and the job file to be deleted. The related file::version path in src/Filesystem/Asset.php also accepted ../ sequences outside the intended index root. This issue is fixed in versions 4.9.5 and 5.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-75594</guid>
    </item>
    <item>
      <title>GHSA-9vx2-j98c-p72w — Kirby: Access to image files and limited access to JSON files outside of the site root via path traversal in the media…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-9vx2-j98c-p72w</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 that are deployed to a server that allows requests for URLs with encoded slashes (`%2f`), such as nginx, PHP&amp;#39;s built-in server or Apache setups that have the option `AllowEncodedSlashes` enabled.
 
It was possible to create and access thumbnails from media files in arbitrary accessible directories on the server that have a valid thumbnail configuration (JSON job file). It was also possible to detect the presence of files with the `.json` file extension anywhere on the server.
 
**This vulnerability is of high severity for affected sites.**
 
Server setups using Apache&amp;#39;s default configuration or other servers that have been hardened against encoded slashes in URLs are *not* affected.&lt;/p&gt;
&lt;p&gt;----&lt;/p&gt;
&lt;p&gt;### Introduction&lt;/p&gt;
&lt;p&gt;A path traversal (also known as directory traversal) vulnerability occurs when untrusted input is used to build a filesystem path without properly confining the result to an intended base directory. By injecting sequences such as `../`, an attacker can escape that directory and reach files elsewhere on the server.&lt;/p&gt;
&lt;p&gt;### Affected components&lt;/p&gt;
&lt;p&gt;Kirby&amp;#39;s media handler processes requests for files in the `media` directory that have not been generated yet. It parses the provided path and finds the correct file or asset from which to generate a thumbnail. Each thumbnail needs to have a prepared job file (a metadata file with file extension `.json`) in order to allow the media handler to generate it.
 
Each parent (such as a page…&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 that are deployed to a server that allows requests for URLs with encoded slashes (`%2f`), such as nginx, PHP&amp;#39;s built-in server or Apache setups that have the option `AllowEncodedSlashes` enabled.
 
It was possible to create and access thumbnails from media files in arbitrary accessible directories on the server that have a valid thumbnail configuration (JSON job file). It was also possible to detect the presence of files with the `.json` file extension anywhere on the server.
 
**This vulnerability is of high severity for affected sites.**
 
Server setups using Apache&amp;#39;s default configuration or other servers that have been hardened against encoded slashes in URLs are *not* affected.&lt;/p&gt;
&lt;p&gt;----&lt;/p&gt;
&lt;p&gt;### Introduction&lt;/p&gt;
&lt;p&gt;A path traversal (also known as directory traversal) vulnerability occurs when untrusted input is used to build a filesystem path without properly confining the result to an intended base directory. By injecting sequences such as `../`, an attacker can escape that directory and reach files elsewhere on the server.&lt;/p&gt;
&lt;p&gt;### Affected components&lt;/p&gt;
&lt;p&gt;Kirby&amp;#39;s media handler processes requests for files in the `media` directory that have not been generated yet. It parses the provided path and finds the correct file or asset from which to generate a thumbnail. Each thumbnail needs to have a prepared job file (a metadata file with file extension `.json`) in order to allow the media handler to generate it.
 
Each parent (such as a page…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-9vx2-j98c-p72w</guid>
    </item>
  </channel>
</rss>
