CVE-2026-48524: PyJWT is a JSON Web Token implementation in Python

Q: How do I fix CVE-2026-48524?

pyjwt: upgrade to 2.13.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-48524 being exploited?

CVE-2026-48524 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-48524 affect?

CVE-2026-48524 affects pyjwt. Severity is low (CVSS 3.7). PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rate limiting. Since kid comes from the unv

Q: How urgent is CVE-2026-48524?

Priority 26/100. Remotely exploitable, no login, no user action

Routine

LOW 3.7REMOTEUPGRADE

CVE-2026-48524 is a low-severity flaw (CVSS 3.7) affecting pyjwt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rate limiting. Since kid comes from the unverified token header, an attacker can trigger unlimited outbound requests. The vulnerability surfaces only when a JWKS fetch fails; an attacker can attempt to provoke that with sustained unknown-kid traffic, bu

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	3.7 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-460, CWE-755
Published	2026-05-28
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: pyjwt project

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-28 16:16 UTCPublished CVE record published
2026-10-26 13:10 UTCUpdated Record last modified

pyjwt project pyjwt UPGRADE

Affected: < 2.13.0

Fixed in: 2.13.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pyjwt || rpm -q pyjwt || pyjwt --version

2. UPGRADE to 2.13.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pyjwt

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pyjwt

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-48524?

pyjwt: upgrade to 2.13.0. Exact commands for each OS are on this page.

Is CVE-2026-48524 being exploited?

CVE-2026-48524 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-48524 affect?

CVE-2026-48524 affects pyjwt. Severity is low (CVSS 3.7). PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rate limiting. Since kid comes from the unv

How urgent is CVE-2026-48524?

Priority 26/100. Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities

Related CVEs

CVE-2026-48526 HIGH 7.4 UPGRADE PyJWT is a JSON Web Token implementation in Python
CVE-2026-48522 MEDIUM 4.2 UPGRADE PyJWT is a JSON Web Token implementation in Python
CVE-2026-48525 MEDIUM 5.3 UPGRADE PyJWT is a JSON Web Token implementation in Python
CVE-2026-48523 MEDIUM 5.4 UPGRADE PyJWT is a JSON Web Token implementation in Python
CVE-2026-103001 MEDIUM 6.5 UPGRADE PyJWT is a Python implementation of JSON Web Token standards

References

← Back to latest CVEs