# CVE-2026-42137: cms — Fixed in 4.9.0 🐘 Packagist Not in CISA KEV # CVE-2026-42137 — cms CVE-2026-42137 is a CWE-862 vulnerability in getkirby/cms. A fix is available for getkirby/cms — see the affected versions and patch details below. Kirby: \`pages.access/list\` and \`files.access/list\` permissions are not consistently checked in the REST API and changes dialog Also known as[GHSA-85x2-r8xv-ww8c](/vulnerability/GHSA-85x2-r8xv-ww8c) Published May 9, 2026 Updated Oct 28, 2026 Affected 2 pkgs Patched 2 / 2 Exploits None indexed Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42137. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.3%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk 0.00%0.30%0.60%0.90%0.0%0.3%Jun 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## Real-World Exposure 2 pkgs affected 🐘`getkirby/cms`🐘`getkirby/cms` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems. ## Description #### TL;DR This vulnerability affects all Kirby sites where users of a particular role have no permission to access or list pages or files (`pages.access`, `pages.list`, `files.access` or `files.list` permission is disabled). This can be due to configuration in the user blueprint(s), via `options` in the model blueprint(s) or via a combination of both settings. **This vulnerability is of high severity for affected sites.** Consumers' Kirby sites are _not_ affected if they intend all users to be able to access all pages and files of the site. The vulnerability can only be exploited by authenticated users. Write actions are _not_ affected by this vulnerability. * * * #### Introduction Missing authorization allows authenticated users to perform actions they are not intended to have access to. The effects of missing authorization can include unauthorized access to sensitive information as well as unauthorized changes to content or system information. #### Impact Kirby's user permissions control which user role is allowed to perform specific actions to content models in the CMS. These permissions are defined for each role in the user blueprint (`site/blueprints/users/...`). It is also possible to customize the permissions for each target model in the model blueprints (such as in `site/blueprints/pages/...`) using the `options` feature. The permissions and options together control the authorization of user actions. Kirby provides the `pages.access`, `pages.list`, `files.access` and `files.list` permissions (among others). The `list` permissions control whether affected models appear in lists throughout the Panel and REST API. The `access` permissions have the same effect but also disable direct access to the affected models. In affected releases, Kirby did not consistently hide non-listable models (models for which the respective `access` or `list` permission was disabled) in the following scenarios: - The changes dialog in the Panel listed changed models even if they were not listable. - The REST API respected the permissions during direct model access, but did not consistently filter collections as well as related models that are included in the API responses for convenience. This includes: - missing permission checks for children, drafts, files, parents and siblings of pages, - missing permission checks for parents and siblings (`next`/`nextWithTemplate` , `prev`/`prevWithTemplate`) of files, - missing permission checks for children, drafts and files of the site model, - missing permission checks for files of users, - incorrect permission checks for `pages.access` instead of `pages.list` for the site and pages children and search routes and - incorrect permission checks for `files.access` instead of `files.list` for the account, site, pages and users files and search routes, - The Panel images for site, pages and users were displayed in lists of the parent model even if the image files were not listable. - The link targets for the previous and next files in the files view were not gated by the files being listable. #### Patches The problem has been patched in [Kirby 4.9.0](https://github.com/getkirby/kirby/releases/tag/4.9.0) and [Kirby 5.4.0](https://github.com/getkirby/kirby/releases/tag/5.4.0). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability. In all of the mentioned releases, we have added permission checks for `$model->isListable()` in all of the affected places. This ensures that results are filtered by the listable property, thereby enforcing the `pages.access`, `pages.list`, `files.access` and `files.list` permissions consistently. ## Affected Packages 2 total 2 fixed Ecosystem Package Vulnerable range Fix 🐘Packagist `getkirby/cms` all versions 4.9.0`composer require getkirby/cms:^4.9.0` 🐘Packagist `getkirby/cms` ≥ 5.0.0&&< 5.4.0 5.4.0`composer require getkirby/cms:^5.4.0` ## Affected Products 1 product · 2 configurations Application `kirby`getkirby ≥ 5.0.0 && < 5.4.0 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update getkirby/cms to 4.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42137 is resolved across your whole dependency graph. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Frequently Asked Questions \### TL;DR This vulnerability affects all Kirby sites where users of a particular role have no permission to access or list pages or files (\`pages.access\`, \`pages.list\`, \`files.access\` or \`files.list\` permission is disabled). This can be due to configuration in the user blueprint(s), via \`options\` in the model blueprint(s) or via a combination of both settings. \*\*This vulnerability is of high severity for affected sites.\*\* Consumers' Kirby sites are \*not\* affected if they intend all users to be able to access all pages and files of the site. The vulnerability can only be exploited by authent O3 Security · Impact-Aware SCA ### Is CVE-2026-42137 in your dependencies? Find it across Packagist, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)