Authorization Bypass Through User-Controlled Key Affecting python-jwt package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.26% (16th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-PYTHONJWT-20418895
  • published4 Oct 2026
  • disclosed15 Aug 2026

Introduced: 15 Aug 2026

CVE-2026-18500  (opens in a new tab)
CWE-639  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 python-jwt.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-jwt package and not the python-jwt package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

@fastify/jwt is a JSON Web Token plugin for Fastify. In versions before 10.2.2, a per-request verification key passed to request.jwtVerify({ key }) is silently overridden by the plugin's globally configured secret, because the option merge applies the global key last. Applications that use different keys for different authorization domains, for example separate user and admin keys, therefore accept a token signed with the global key on a route that explicitly requires another key. This lets an ordinary authenticated user cross a key-based trust boundary without knowing either secret. The issue is fixed in @fastify/jwt 10.2.2, where an explicit per-call key takes precedence over the global secret. Users should upgrade to 10.2.2.

CVSS Base Scores

version 3.1