CVE-2026-22706

Summary of CVE-2026-22706 Vulnerability Details

• CVE: CVE-2026-22706
• CVSS v3.1 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 (2.1, Low)
• Affected Versions: @strapi/admin and @strapi/plugin-users-permissions <=5.33.2
• How to Patch: Immediately update your Strapi to >=5.33.3

Description of CVE-2026-22706

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

IoC's for CVE-2026-22706

Indicators that an instance running an unpatched version may have been exploited:

• Successful POST /api/auth/refresh or POST /admin/access-token requests using a refresh token issued before the user's most recent password change. Reviewable by correlating refresh-token iat claims against password-change events in audit logs
• New access-token issuances for a user whose password was reset within the past 30 days, originating from an IP or User-Agent that did not perform the reset
• Multiple active refresh tokens for a single user across distinct IPs after a password reset event
• Database query: rows in strapi_session with created_at earlier than the user's most recent password-reset timestamp and status = 'active'

References

• OWASP ASVS 4.0 – V2.1.1: Session invalidation on credential change
• OWASP Top 10 – A2: Broken Authentication

Credits

• bugbunny.ai
• AndyAnh174 (concurrent report, 2026-04-09, originally filed as GHSA-c6gj-8rxm-jrf2, closed as duplicate)
• Aastha2602 (concurrent report, 2026-03-10, originally filed as GHSA-5qvg-4jch-gvf4, closed as duplicate)

Kodem intelligence

1. What is CVE-2026-22706? CVE-2026-22706 is a low-severity security vulnerability in @strapi/admin (npm), affecting versions <= 5.33.2. It is fixed in 5.33.3.
2. Which packages are affected by CVE-2026-22706?
   • @strapi/admin (npm) (versions <= 5.33.2)
   • @strapi/plugin-users-permissions (npm) (versions <= 5.33.2)
3. Is there a fix for CVE-2026-22706? Yes. CVE-2026-22706 is fixed in 5.33.3. Upgrade to this version or later.
4. Is CVE-2026-22706 exploitable, and should I be worried? Whether CVE-2026-22706 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-22706 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-22706?
   • Upgrade @strapi/admin to 5.33.3 or later
   • Upgrade @strapi/plugin-users-permissions to 5.33.3 or later