CVE-2026-22706
Description
Strapi is an open source headless content management system. In Strapi versions prior to 5.33.3, changing or resetting a user's password did not invalidate the user's existing refresh-token sessions by default. The refresh-token invalidation step in the users-permissions and admin authentication controllers was conditional on a caller-supplied `deviceId`. When a password change or reset request did not include a `deviceId`, no refresh tokens were revoked, leaving every prior session active. An attacker who had previously obtained a refresh token could continue minting new access tokens after the legitimate user reset their password, allowing persistent unauthorized access for the lifetime of the refresh token (up to 30 days by default). Rotating credentials no longer terminated an active attacker session, defeating password reset as a containment measure. The patch in version 5.33.3 invalidates all refresh tokens associated with the user on every password change and password reset, regardless of whether a `deviceId` is supplied. A new device-scoped session is then issued to the caller as part of the response.
How to fix
- strapi strapi5.33.3 or later
- @strapi/admin5.33.3 or later
- @strapi/plugin-users-permissions5.33.3 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| strapi strapi | v < 5.33.3 | 5.33.3 |
| @strapi/adminnpm | v < 5.33.3 | 5.33.3 |
| @strapi/plugin-users-permissionsnpm | v < 5.33.3 | 5.33.3 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.