CVE-2026-22706 PUBLISHED

Strapi: Password Reset Does Not Revoke Existing Refresh Sessions

Assigner: GitHub_M
Reserved: 08.01.2026 Published: 14.05.2026 Updated: 14.05.2026

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.

Metrics

CVSS Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
CVSS Score: 2.1

Product Status

Vendor strapi
Product strapi
Versions
  • Version < 5.33.3 is affected
Vendor strapi
Product @strapi/admin
Versions
  • Version < 5.33.3 is affected
Vendor strapi
Product @strapi/plugin-users-permissions
Versions
  • Version < 5.33.3 is affected

References

Problem Types

  • CWE-613: Insufficient Session Expiration CWE