Allocation of Resources Without Limits or Throttling Affecting py3.14-jwt package, versions <2.14.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.35% (27th 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-MINIMOSLATEST-PY314JWT-20345053
  • published1 Oct 2026
  • disclosed28 Sept 2026

Introduced: 28 Sep 2026

NewCVE-2026-101917  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Minimos:latest py3.14-jwt to version 2.14.0-r0 or higher.

NVD Description

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

PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT get_signing_key_from_jwt is affected because unknown kid misses force refreshes without a negative cache or minimum refresh interval. This occurs when unauthenticated tokens repeatedly use the same unknown kid or varying kid values absent from the cached JWKS. As a result, each cache miss causes PyJWKClient to refresh the JWKS. Consequently, attacker traffic can amplify outbound requests to the configured JWKS endpoint. This issue is fixed in version 2.14.0.

CVSS Base Scores

version 3.1