cve.bz

CVE-2026-48523 pyjwt project pyjwt

5.4 mediumExploit referenceEPSS 0.1%Fix available

Medium (5.4) in pyjwt project pyjwt. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in pyjwt 2.12.1, 2.13.0.

On this page
PyJWT is a JSON Web Token implementation in Python. From 2.9.0 to 2.12.1, there is a verifier-side algorithm allow-list bypass when jwt.decode() or jwt.decode_complete() are called with a PyJWK key. The token header alg is checked against the caller-supplied algorithms allow-list, but signature verification is performed with the algorithm bound to the PyJWK object instead of the header algorithm. An attacker who controls a registered JWK/JWKS private key can sign with a disallowed algorithm, advertise an allowed algorithm in the JWT header, and still be accepted. The issue affects the documented PyJWKClient.get_signing_key_from_jwt(...) flow. This vulnerability is fixed in 2.13.0.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-05-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-48523 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48523?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48523?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48523 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
pyjwt_project:pyjwtfrom 2.9.0 before 2.13.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jq35-7prp-9v3fPyPIpyjwt>=2.9.0 <2.13.02.13.0
PYSEC-2026-176PyPIpyjwt>=2.9.0 <2.12.12.12.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13pyjwtno fix listedDEBIAN-CVE-2026-48523
Debian14pyjwt2.13.0-1DEBIAN-CVE-2026-48523
Ubuntu22.04:LTSpyjwt2.3.0-1ubuntu0.4USN-8823-1
Ubuntu24.04:LTSpyjwt2.7.0-1ubuntu0.2USN-8823-1
Ubuntu25.10pyjwtno fix listedUBUNTU-CVE-2026-48523
Ubuntu26.04:LTSpyjwt2.10.1-4ubuntu1.1UBUNTU-CVE-2026-48523 USN-8823-1
UbuntuPro:16.04:LTSpyjwt1.3.0-1ubuntu0.1+esm2USN-8823-1
UbuntuPro:18.04:LTSpyjwt1.5.3+ds1-1ubuntu0.1+esm2USN-8823-1
UbuntuPro:20.04:LTSpyjwt1.7.1-2ubuntu2.1+esm2USN-8823-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 9 morepython-PyJWT2.4.0-150200.3.14.1SUSE-SU-2026:2627-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 9 morepython-PyJWT2.8.0-150400.8.13.1SUSE-SU-2026:2626-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0python-PyJWT2.12.1-160000.2.1SUSE-SU-2026:22170-1
SUSELinux Micro 6.0python-PyJWT2.9.0-3.1SUSE-SU-2026:22238-1
SUSELinux Micro 6.1python-PyJWT2.12.1-slfo.1.1_2.1SUSE-SU-2026:22138-1
SUSELinux Micro 6.2python-PyJWT2.12.1-160000.2.1SUSE-SU-2026:22220-1
openSUSELeap 16.0python-PyJWT2.12.1-160000.2.1openSUSE-SU-2026:21095-1
openSUSETumbleweedpython-PyJWT2.13.0-1.1openSUSE-SU-2026:11024-1
Alpaquita25, streampy3-jwt2.13.0-r0BELL-CVE-2026-48523

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw is rated as Moderate. It impacts applications using PyJWT with PyJWK keys, specifically when jwt.decode() or jwt.decode_complete() are called with a PyJWK key and the PyJWKClient.get_signing_key_from_jwt flow. An attacker must control a registered JWK private key to bypass algorithm allow-lists, limiting the exploitability in environments with strict key management.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Fix deferred
OpenShift Lightspeedopenshift-lightspeed/lightspeed-ocp-rag-rhel9Fix deferred
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Fix deferred
OpenShift Lightspeedopenshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-cpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-cuda-rhel9Not affected
Red Hat AI Inference Serverrhaiis/vllm-rocm-rhel9Not affected
Red Hat AI Inference Serverrhaiis/vllm-tpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-cpu-rhel9Not affected
Red Hat AI Inference Serverrhaii/vllm-cuda-rhel9Not affected
Red Hat AI Inference Serverrhaii/vllm-gaudi-rhel9Not affected
Red Hat AI Inference Serverrhaii/vllm-neuron-rhel9Not affected
Red Hat AI Inference Serverrhaii/vllm-rocm-rhel9Not affected
Red Hat AI Inference Serverrhaii/vllm-spyre-rhel9Not affected
Red Hat AI Inference Serverrhaii/vllm-tpu-rhel9Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-supported-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9Fix deferred
65 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-48523.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON