dbcve.org
StrapiApplication

CVE-2026-22706

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 5.33.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Strapi versions before 5.33.3, the refresh-token invalidation logic during password changes and resets required a caller-supplied deviceId. When no deviceId was provided, no refresh tokens were revoked, leaving all prior sessions active. An attacker with a previously stolen refresh token could continue generating access tokens for up to 30 days after the legitimate user reset their password, defeating password reset as a security control.

MitigationUpgrade to Strapi version 5.33.3 or later, which invalidates all user refresh tokens on every password change or reset regardless of deviceId.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StrapiApplication
Affected:< 5.33.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Strapi version
    Run 'npm list @strapi/strapi' or check package.json to determine the exact Strapi version installed in your environment
    Affected if The installed version is lower than 5.33.3 (e.g., 5.0.0 through 5.33.2)
  2. Verify refresh token configuration
    Check your Strapi configuration files (typically config/plugins.js or .env) for authentication settings related to refresh tokens, particularly the token expiration duration
    Affected if Refresh tokens are enabled with a long expiration (up to 30 days as mentioned in the CVE description) and the configuration does not enforce deviceId-based invalidation
  3. Review token invalidation logic
    Examine the source code for password change and reset endpoints (typically in /src/api/auth or similar controllers) to verify how refresh token invalidation is handled, specifically looking for whether deviceId is required
    Affected if The code shows that when deviceId is not provided in the password change/reset request, no refresh tokens are revoked (the vulnerability condition)
  4. Test password reset behavior
    Create a test scenario: obtain a valid refresh token, perform a password change/reset without specifying a deviceId, then attempt to use the original refresh token to obtain a new access token
    Affected if The original refresh token still works after the password change, confirming no invalidation occurred

You are affected if your Strapi version is below 5.33.3 and refresh tokens remain valid after a password change or reset when no deviceId is explicitly provided.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.33.3 or later
Fixed in 5.33.3
Interim mitigation

Upgrade to Strapi version 5.33.3 or later, which invalidates all user refresh tokens on every password change or reset regardless of deviceId.

Recommended fix High confidence

Strapi 5.33.3

  1. Upgrade Strapi to version 5.33.3 or later by updating the Strapi dependency in your package.json file
  2. Run `npm install` or `yarn install` to install the updated version
  3. Restart your Strapi application to load the patched version
  4. Verify the upgrade was successful by checking the Strapi version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Strapi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22706 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22706 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data