Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-48526: CWE-287: Improper Authentication in jpadilla pyjwt

0
High
VulnerabilityCVE-2026-48526cvecve-2026-48526cwe-287cwe-347
Published: Thu May 28 2026 (05/28/2026, 15:09:09 UTC)
Source: CVE Database V5
Vendor/Project: jpadilla
Product: pyjwt

Description

PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens, while supporting both asymmetric and HMAC algorithms, the library does not validate use of JSON Web Keys in HMAC algorithm, allowing attacker to use the issuer public key as the secret key for HMAC algorithm. This vulnerability is fixed in 2.13.0.

CVSS v3.1

Score 7.4high

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 05/28/2026, 15:48:27 UTC

Technical Analysis

PyJWT is a Python library for JSON Web Token implementation. Before version 2.13.0, when decoding JWTs supporting both asymmetric and HMAC algorithms, the library did not properly validate the use of JSON Web Keys in HMAC algorithms. This allowed an attacker to use the issuer's public key as the secret key for HMAC, bypassing intended authentication controls. This vulnerability is tracked as CVE-2026-48526 and is classified under CWE-287 and CWE-347. The vulnerability has a CVSS score of 7.4, reflecting a high impact on confidentiality and integrity but no impact on availability. The issue is resolved in PyJWT 2.13.0.

Potential Impact

Successful exploitation could allow an attacker to forge or manipulate JSON Web Tokens by using the issuer's public key as the HMAC secret key, potentially leading to unauthorized access or privilege escalation. The vulnerability impacts the confidentiality and integrity of JWT-based authentication mechanisms. There are no known exploits in the wild as of the published date.

Mitigation Recommendations

Upgrade PyJWT to version 2.13.0 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 2.13.0, applying this official fix is the recommended remediation. No other mitigation or temporary workaround is indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-05-21T16:18:10.619Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a186056e29bf47b500b42de

Added to database: 5/28/2026, 3:33:42 PM

Last enriched: 5/28/2026, 3:48:27 PM

Last updated: 5/28/2026, 10:53:51 PM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses