CVE-2026-110024 @fastify/jwt vulnerable to missing token expiration when per-call options drop global defaults
Attackers can use never-expiring JWTs because per-call options override global expiration settings, bypassing token validity checks in @fastify/jwt.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-110024?
CVE-2026-110024 is a medium-severity vulnerability in @fastify/jwt, published on 18 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-613
Which versions are affected by CVE-2026-110024?
How do I fix CVE-2026-110024?
No fix has been published for CVE-2026-110024 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-110024 being exploited?
There is no known exploitation of CVE-2026-110024 in the wild and no public exploit code.
Sources
Also known as GHSA-f5gh-84pj-v2pg.