Intel

AIKIDO-2026-631530

@fastify/jwt is vulnerable to Authorization Bypass

Authorization BypassCVE-2026-18500 Published 3 days ago

81

High Risk

This Affects:

JS@fastify/jwt
0.0.1 - 10.2.1
Fixed in 10.2.2
Are you affected? Scan for Free

TL;DR

@fastify/jwt lets a route pass a key to request.jwtVerify() or reply.jwtSign() to scope a token to a specific authorization domain. The resolved global secret overrides that key before signature verification, so the supplied key was ignored. Applications that use separate keys for different domains would accept a token signed with the global secret on a route that explicitly required a different key. The fix verifies the key so verification and signing use the key actually supplied by the route.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you pass an explicit key to request.jwtVerify() or reply.jwtSign() to enforce an authorization boundary between different JWT keys.

Background info

@fastify/jwt is vulnerable to Authorization Bypass in versions 0.0.1 - 10.2.1.

How to fix this

Upgrade the @fastify/jwt library to the patch version.