CVE-2026-22706 — @strapi/admin
CVE-2026-22706 is a CWE-613 vulnerability in @strapi/admin. A fix is available for @strapi/admin — see the affected versions and patch details below.
Strapi: Password Reset Does Not Revoke Existing Refresh Sessions
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22706.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@strapi/adminnpm@strapi/plugin-users-permissionsnpmDescription
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/adminand@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/refreshorPOST /admin/access-tokenrequests using a refresh token issued before the user's most recent password change. Reviewable by correlating refresh-tokeniatclaims 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_sessionwithcreated_atearlier than the user's most recent password-reset timestamp andstatus = '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)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @strapi/admin | all versions | 5.33.3npm install @strapi/admin@5.33.3 |
| 📦npm | @strapi/plugin-users-permissions | all versions | 5.33.3npm install @strapi/plugin-users-permissions@5.33.3 |
Affected Products
strapistrapiDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/admin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @strapi/admin to 5.33.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22706 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-22706 in your dependencies?
Find it across npm, including transitive dependencies.