# Kirby: Access to image files outside of the site root via path traversal in the media handling

Advisory record · `GHSA-6j4c-mgqr-qv76`

- **Identifiers:** `GHSA-6j4c-mgqr-qv76` · `CVE-2026-75592` · `PKSA-cmzk-n5t6-2v3k`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 2 Sept 2026
- **Updated:** 2 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Sept 2026, 14:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `getkirby/cms` (Packagist): affected `<4.9.5 || >=5.0.0, <5.5.2`; fixed in `4.9.5`, `5.5.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Kirby's media handler in the getkirby/cms Packagist package, versions before 4.9.5 and from 5.0.0 before 5.5.2, has a path traversal flaw in its containment checks. A sibling directory whose name starts with the same prefix as the site's index root can pass those checks. The source describes the impact as access to media files with job files stored in such sibling directories, which can lead to information leaks and deletion of the job file; it does not say what an attacker must already have, so the exact prerequisites are unclear. Upgrade to Kirby 4.9.5 or 5.5.2, or a later version.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0068, the 52nd percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:06 UTC: First seen by agentprime
- 31 Oct 2026, 14:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6j4c-mgqr-qv76)

## Sources

- [GitHub Advisory Database: GHSA-6j4c-mgqr-qv76](https://github.com/advisories/GHSA-6j4c-mgqr-qv76)
- [OSV: GHSA-6j4c-mgqr-qv76](https://osv.dev/vulnerability/GHSA-6j4c-mgqr-qv76)
- <https://github.com/getkirby/kirby/security/advisories/GHSA-6j4c-mgqr-qv76>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-75592>
- <https://github.com/getkirby/kirby/commit/2b6fab950bc89d505ea89576bf71c8de614cc3b2>
- <https://github.com/getkirby/kirby/commit/e0dca5f709adc21b36f5549df2c0619bc59da56c>
- <https://github.com/getkirby/kirby>
- <https://github.com/getkirby/kirby/releases/tag/4.9.5>
- <https://github.com/getkirby/kirby/releases/tag/5.5.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6j4c-mgqr-qv76>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6j4c-mgqr-qv76/>. Everything for agents: <https://agentprime.io/llms.txt>.
