Intel

AIKIDO-2026-921776

jwt-simple is vulnerable to Improper Authentication

Improper AuthenticationGHSA-vgc9-f48j-3xvj Published Aug 3, 2026

75

High Risk

This Affects:

RUSTjwt-simple
0.12.14 - 0.12.17
Fixed in 0.13.0
Are you affected? Scan for Free

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.

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.

Background info

jwt-simple is vulnerable to Improper Authentication in versions 0.12.14 - 0.12.17.

How to fix this

Upgrade the jwt-simple library to the patch version.

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform