All vulnerabilities
CVE-2026-107275GHSA-9x4w-r9p5-5h7m

@fastify/jwt vulnerable to missing token expiration when temporal options cannot be parsed

@fastify/jwt @fastify/jwtFrameworks
CVSS
6.8Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.31%Chance of exploitation activity in the next 30 days, higher than 22% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in10.2.3Fixed versionCVE List
Published8 Oct 2026Updated 8 Oct 2026CVE List

What fixes it

  • 10.2.3@fastify/jwtCVE List
  • 10.2.3@fastify/jwt, npmGitHubnpm install @fastify/jwt@10.2.3

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 JSON Web Token plugin for the Fastify web framework. In versions before 10.2.3, a time span passed to expiresIn, notBefore, or maxAge that the plugin's parser cannot read, such as a compound span, a month unit, an ISO 8601 duration, a decimal comma, or a value with surrounding whitespace, is silently dropped instead of refused. On the signing path this produces a token with no expiration claim that never expires, and on the verification path a configured maxAge stops being enforced, so a token that should be rejected for age is accepted. The issue is fixed in @fastify/jwt 10.2.3, and users should upgrade to 10.2.3 or later. As a workaround, pass these options as a number of seconds, or verify that any time-span string parses to a finite value before relying on it.

Text from CVE List

Affected versions 3

  • @fastify/jwtaffected: all versions before 10.2.3CVE List
  • @fastify/jwtunaffected: 10.2.3CVE List
  • @fastify/jwt, npm< 10.2.3GitHub

References 2