CVE-2026-75594: Kirby: Access to image files and limited access to JSON files outside of the site root via path traversal in the media handling
Kirby is an open-source content management system. Prior to 4.9.5 and 5.5.2, depending on the release line, Kirby'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'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'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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Kirbyto a version that resolves this vulnerability.Fixed in 4.9.5 - Upgrade
Upgrade
Kirbyto a version that resolves this vulnerability.Fixed in 5.5.2
Event History
Frequently Asked Questions
Which deployments are exposed to remote exploitation?
Deployments running a vulnerable Kirby release are exposed when hosted on nginx, PHP's built-in server, or Apache with AllowEncodedSlashes enabled. These environments can pass encoded slash characters in a filename to the affected media handler.
What does an attacker need to send to exploit the media-handler issue?
The attacker needs to submit a filename containing encoded slash characters, such as %2f, so that the filename traverses outside the validated parent media directory. No authentication requirement is specified in the available information.
What information or files could be exposed or altered?
Response differences can reveal whether arbitrary .json files exist. If a reachable .json file contains a valid filename key, Kirby can return the image referenced by that key and delete the job file; the related file::version path also accepts ../ traversal outside its intended index root.
Which versions contain the fix?
Update to Kirby 4.9.5 on the 4.x release line or 5.5.2 on the 5.x release line. Versions prior to those releases are affected.