Skip to main content
VulnerabilityPublished Updated

CVE-2026-102267: jpadilla pyjwt · Information Exposure

Affects jpadilla pyjwtSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 2.14.0 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.14.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade jpadilla pyjwt to 2.14.0.

Affected software

ProductAffectedFixed in
jpadillapyjwtAffected
  • <2.14.0
Fixed in
  • 2.14.0
PyPIpyjwtpkg:pypi/pyjwtOther threatsAffected
  • <2.14.0
Fixed in
  • 2.14.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade PyJWT to version 2.14.0 or later, which includes the fix that disables automatic HTTP redirects during JWKS fetches. This prevents exposure of sensitive headers and JWKS trust poisoning. No additional action is required if the application uses PyJWT 2.14.0 or later.

Description

PyJWT versions prior to 2.14.0 contain a vulnerability in the PyJWKClient component where HTTP redirects during JWKS fetching are followed without validating the redirect destination. This can lead to exposure of sensitive request headers and allow an attacker-influenced redirect to poison JWKS trust, potentially causing acceptance of forged JWTs. The issue requires an attacker to influence the configured JWKS endpoint's response and is not triggered by token key IDs alone. The vulnerability is fixed in PyJWT 2.14.0.

References

Community reviews

Loading reviews…