# CVE-2026-27939: cms PrivEsc — Fixed in 6.4.0 🐘 🐘 Packagist Not in CISA KEV HIGH severity # CVE-2026-27939 — cms HIGH [Fix: statamic/cms@8639ef9](https://github.com/statamic/cms/commit/8639ef96217eaa682bc42e8a62769cb7c6a85d3a) CVE-2026-27939 is a high-severity (CVSS 8.8) Improper Authentication vulnerability in statamic/cms. A fix is available for statamic/cms — see the affected versions and patch details below. Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass Also known as[GHSA-rw9x-pxqx-q789](/vulnerability/GHSA-rw9x-pxqx-q789) Published Feb 27, 2026 Updated Oct 28, 2026 Affected 1 pkg Patched 1 / 1 Exploits None indexed Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - A successful exploit gives an attacker total control of the affected component, not partial access. - 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-27939. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.4%probability of exploitation in next 30 days Lower Risk\-0.03% Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk 0.00%0.32%0.64%0.96%0.4%0.4%0.5%0.4%Jul 26Oct 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 1 pkg affected 🐘`statamic/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 Statmatic is a Laravel and Git powered content management system (CMS). Starting in version 6.0.0 and prior to version 6.4.0, Authenticated Control Panel users may under certain conditions obtain elevated privileges without completing the intended verification step. This can allow access to sensitive operations and, depending on the user’s existing permissions, may lead to privilege escalation. This has been fixed in 6.4.0. ## Affected Packages 1 total 1 fixed Ecosystem Package Vulnerable range Fix 🐘Packagist `statamic/cms` ≥ 6.0.0&&< 6.4.0 6.4.0`composer require statamic/cms:^6.4.0` ## Affected Products 1 product · 1 configurations Application `statamic`statamic ≥ 6.0.0 && < 6.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 statamic/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update statamic/cms to 6.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27939 is resolved across your whole dependency graph. 3. ### Workarounds Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable. ## Frequently Asked Questions Statmatic is a Laravel and Git powered content management system (CMS). Starting in version 6.0.0 and prior to version 6.4.0, Authenticated Control Panel users may under certain conditions obtain elevated privileges without completing the intended verification step. This can allow access to sensitive operations and, depending on the user’s existing permissions, may lead to privilege escalation. This has been fixed in 6.4.0. O3 Security · Impact-Aware SCA ### Is CVE-2026-27939 in your dependencies? Find it across Packagist, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)