Skip to content
Laskyr

craftcms/cms security advisory

CVE-2026-27128: Craft CMS Race condition in Token Service potentially allows for token usage greater than the token limit

CVE-2026-27128 is a medium-severity privilege escalation vulnerability in the PHP package craftcms/cms (CVSS 4.8), published 24 February 2026. The advisory does not name a fixed version. Exploiting it needs an admin-level account.

medium 4.8 published 2026-02-24 · updated 2026-06-17

The advisory does not name a fixed version

This privilege escalation issue affects craftcms/cms in 2 release lines: >= 4.5.0-RC1, <= 4.16.18; >= 5.0.0-RC1, <= 5.8.22. The newest release (5.12.0) is outside the affected range.

Affected versions
>= 4.5.0-RC1, <= 4.16.18
>= 5.0.0-RC1, <= 5.8.22
Fixed in
not stated
Newest release
5.12.0
Severity
Medium · CVSS 4.8
Type
Privilege escalation
CWE-367
Exploited in the wild
Not on the CISA KEV list
checked 2026-11-04

Is your craftcms/cms version affected?

Run composer show craftcms/cms in your project, then enter the version. We check it against this and every other known craftcms/cms advisory.

Who can exploit CVE-2026-27128

CVSS vector (scored by NVD): CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Your app is only exposed if it uses the affected part of craftcms/cms. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-27128 in craftcms/cms

  1. Find the installed version: composer show craftcms/cms. If you never required it yourself, composer why craftcms/cms shows which package pulls it in.
  2. Update it: composer update craftcms/cms --with-all-dependencies.
  3. If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "craftcms/cms": "^5.12.0" if you can take that version), or upgrade the package that requires it.
  4. Run composer audit. It reads the same advisory data and should no longer list CVE-2026-27128.
  5. Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for privilege escalation issues while the upgrade waits. None of it replaces the fix.

The CVE-2026-27128 advisory

Craft is a content management system (CMS). In versions 4.5.0-RC1 through 4.16.18 and 5.0.0-RC1 through 5.8.22, a Time-of-Check-Time-of-Use (TOCTOU) race condition exists in Craft CMS’s token validation service for tokens that explicitly set a limited usage. The `getTokenRoute()` method reads a token’s usage count, checks if it’s within limits, then updates the database in separate non-atomic operations. By sending concurrent requests, an attacker can use a single-use impersonation token multiple times before the database update completes. To make this work, an attacker needs to obtain a valid user account impersonation URL with a non-expired token via some other means and exploit a race condition while bypassing any rate-limiting rules in place. For this to be a privilege escalation, the impersonation URL must include a token for a user account with more permissions than the current user. Versions 4.16.19 and 5.8.23 patch the issue.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-27128. Advisory title: “Craft CMS Race condition in Token Service potentially allows for token usage greater than the token limit”.

References

Other craftcms/cms advisories

Related

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit