---
id: "CVE-2026-110024"
kind: "vulnerability"
aliases: ["CVE-2026-110024"]
title: "@fastify/jwt: per-call options drop global expiry, so tokens never expire"
severity: "medium"
cvss: 6.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["auth", "fastify", "jwt", "node", "package"]
not_affected_if: ["no-global-expiry-defaults", "route-level-decorators-only"]
published_at: "2026-10-18T15:16:51+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T03:44:55+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110024", "first_seen_at": "2026-10-23T21:57:15+00:00"}]
---

# @fastify/jwt: per-call options drop global expiry, so tokens never expire

Versions of @fastify/jwt before 10.2.5 replace the global sign and verify defaults with per-call options instead of merging them. An attacker can then present tokens that were issued without an expiration or that exceed the configured maximum age, and they are accepted.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `npm ls @fastify/jwt` (or `pnpm why @fastify/jwt`) to find the installed version.
- Search the code for calls to top-level `fastify.jwt.sign(` or `fastify.jwt.verify(` that pass an options object, and check whether the app also sets global defaults such as `expiresIn` or `maxAge` at registration.

## Fix

- Upgrade `@fastify/jwt` to `10.2.5` or later.
- Until upgraded, pass the full set of expiry options on every top-level `sign` and `verify` call, or use the route-level decorators, which already merge options.

## Timeline

- 2026-10-23T21:57:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110024

## From the sources

@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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_