AIKIDO-2026-921776
jwt-simple is vulnerable to Improper Authentication
75
CVE Score
High
Improper Authentication
TL;DR
JWE decryption through the default decrypt_token(&token, None) path does not validate claims, because DecryptionOptions::claim_options defaults to None and validation runs only when explicit options are supplied. Expired or not-yet-valid encrypted tokens are returned as successfully decrypted claims, allowing indefinite replay of expired tokens and acceptance of premature ones. This matters most for the AES key wrap modes, where a decryptable token is reasonably treated as a credential, and jwe is a default build feature. The fix always validates claims with default verification options when none are supplied.
How do I fix this?
Upgrade the jwt-simple library to the patch version.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you decrypt JWE tokens through the default decrypt_token path with the jwe feature enabled.
Package
Versions
0.12.14 - 0.12.17
Fixed in 0.13.0Background info
jwt-simple is vulnerable to Improper Authentication in versions 0.12.14 - 0.12.17.
Get secure today,
quickly and for free.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPAuthorized© All Intel data is openly available and commercially licensed.