Authentication restriction bypass via unpinned JWT algorithm
Published Jun 29, 2026 · Updated Jun 29, 2026
JWT algorithm restriction bypass in Strapi before 5.7.0 allows remote attackers with the JWT secret to mint accepted HS384 or HS512 tokens. The legacy users-permissions JWT verifier passes an empty options object to jwt.verify when no algorithm is configured, so jsonwebtoken accepts any HMAC variant declared in the token header. Exploitation requires possession of the deployment's jwtSecret; the defect broadens accepted algorithms but does not reveal the secret or enable asymmetric-key confusion.
Summary
What happened
JWT algorithm restriction bypass in Strapi before 5.7.0 allows remote attackers with the JWT secret to mint accepted HS384 or HS512 tokens. The legacy users-permissions JWT verifier passes an empty options object to jwt.verify when no algorithm is configured, so jsonwebtoken accepts any HMAC variant declared in the token header. Exploitation requires possession of the deployment's jwtSecret; the defect broadens accepted algorithms but does not reveal the secret or enable asymmetric-key confusion.
The record
- CVE
- CVE-2026-57997
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- Strapi
- Product
- Strapi
- Classifications
- CWE-327, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.7.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo