p PatchFirst

CVE-2026-22706

CVE-2026-22706 · Strapi: Password Reset Does Not Revoke Existing Refresh Sessions

Здесь приведены факты из открытых источников об уязвимостях. Перед обновлением ознакомьтесь с исходным сообщением.

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.

CVSS 2.1 · Низкий · EPSS 0,3% · Есть исправление

Опубликовано
Обновлено

Стек: node

Затронутые продукты и версии

  • strapi

    Версии
    • < 5.33.3: Затронуто

    Нет опубликованного исправления

  • @strapi/admin

    Версии
    • < 5.33.3: Затронуто

    Нет опубликованного исправления

  • @strapi/plugin-users-permissions

    Версии
    • < 5.33.3: Затронуто

    Нет опубликованного исправления

  • @strapi/admin npm

    Затронутые диапазоны версий
    • SEMVER: < 5.33.3

    Обновитесь до 5.33.3

  • @strapi/plugin-users-permissions npm

    Затронутые диапазоны версий
    • SEMVER: < 5.33.3

    Обновитесь до 5.33.3

Первоисточники

Проверьте свой сервер →