@fastify/jwt vulnerable to missing token expiration when per-call options drop global defaults
What fixes it
- 10.2.5@fastify/jwtCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
@fastify/jwt is a JWT utility plugin for Fastify. In versions prior to 10.2.5, the top-level sign and verify methods replace the globally configured defaults with the per-call options instead of merging them, so passing any per-call option silently drops every global default that the call does not restate, including temporal protections such as token expiration and maximum accepted token age. A token signed this way carries no expiration claim and never expires, and verification stops enforcing a configured maximum age, so stale or never-expiring tokens are accepted. The route-level decorators for signing and verifying already merge options and are not affected. The issue is fixed in @fastify/jwt 10.2.5, and users should upgrade to 10.2.5 or later.
Text from CVE List
Affected versions 2
- @fastify/jwtaffected: all versions before 10.2.5CVE List
- @fastify/jwtunaffected: 10.2.5CVE List