CVE-2024-33663VulnerabilityPublished 25 Feb 2026

CVE-2024-33663: python-jose · n/a

Affects python-joseSource CVE Database V5

Mentioned vulnerabilities

CVE-2022-29217

Not known to be exploited · CVSS 6.5 Critical : upgrade to 3.3.1 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.3.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade python-jose to 3.3.1.

Affected software

Product	Affected	Fixed in
PyPIpython-jose`pkg:pypi/python-jose`Other threats	Affected <3.3.1	Fixed in 3.3.1

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

AI-suggested

To mitigate CVE-2024-33663, organizations should immediately identify all applications and services using python-jose versions up to 3.3.0. Although no official patches are currently linked, monitoring the python-jose project for updates or security patches is critical. In the interim, consider the following specific actions: 1) Implement strict input validation and reject tokens or keys that do not conform to expected formats to reduce algorithm confusion risk. 2) Use alternative, well-maintained cryptographic libraries with robust key handling and signature verification if feasible. 3) Employ defense-in-depth by adding additional layers of authentication and authorization checks beyond token validation. 4) Conduct thorough code reviews and security testing focused on cryptographic operations and key management. 5) Monitor logs and alerts for suspicious token validation failures or anomalies indicative of exploitation attempts. 6) Educate developers about the risks of algorithm confusion and proper cryptographic practices. 7) Prepare incident response plans to quickly address potential exploitation. These targeted mitigations go beyond generic advice by focusing on the specific nature of the algorithm confusion and the cryptographic context of python-jose.

Description

python-jose through 3.5.0 fails to properly validate asymmetric keys in HMAC initialization, accepting DER-encoded public keys that lack PEM armor or SSH prefixes. Attackers holding the service's public key can forge HS256 tokens that pass verification when algorithms are not explicitly restricted. This is an incomplete fix for CVE-2024-33663.

Impact

The primary impact of CVE-2024-33663 is the potential compromise of cryptographic integrity and confidentiality in applications using python-jose for token validation or cryptographic operations. Attackers exploiting this vulnerability can bypass signature verification, allowing unauthorized access or privilege escalation by forging tokens or messages. This undermines trust in authentication and authorization mechanisms, potentially leading to data breaches, unauthorized transactions, or exposure of sensitive information. Since python-jose is widely used in Python applications for JWT and JOSE token handling, the vulnerability could affect a broad range of web services, APIs, and cloud-native applications globally. The absence of required authentication or user interaction lowers the barrier for exploitation, increasing risk. However, the lack of known exploits in the wild and the medium CVSS score suggest the threat is moderate but should be addressed promptly to avoid future exploitation. Organizations relying on python-jose in critical infrastructure, financial services, healthcare, or government systems face higher risk due to the sensitivity of data and operations involved.

Summary

CVE-2024-33663 is a cryptographic vulnerability affecting python-jose versions through 3.3.0. The issue arises from algorithm confusion when processing OpenSSH ECDSA keys and other key formats, leading to improper verification of cryptographic signatures. This vulnerability is categorized under CWE-327, which involves the use of broken or risky cryptographic algorithms. The flaw is similar to CVE-2022-29217, indicating a recurring problem in how python-jose handles key formats and signature verification. An attacker can exploit this vulnerability remotely without authentication or user interaction by crafting malicious tokens that exploit the algorithm confusion, potentially allowing them to bypass signature verification. This compromises the confidentiality and integrity of the system relying on python-jose for cryptographic operations, such as JSON Web Tokens (JWT) validation. The vulnerability does not affect availability and has a CVSS 3.1 base score of 6.5, reflecting medium severity. No patches or fixes are currently linked, and no known exploits have been reported in the wild as of the publication date. The vulnerability affects any system or application using vulnerable python-jose versions for cryptographic operations involving ECDSA keys, especially in environments where OpenSSH keys are used or accepted.

CWE-327Use of a Broken or Risky Cryptographic Algorithm (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a broken or risky cryptographic algorithm or protocol.
Architecture and Design · Libraries or Frameworks
When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations.
Architecture and Design
Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms.
Architecture and Design
Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.7 (opens in a new tab)
V2.9.3 (opens in a new tab)
V6.2.2 (opens in a new tab)
Attack patterns
Encryption Brute Forcing (opens in a new tab)
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
Cryptanalysis of Cellular Encryption (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 02:58 UTC

WeaknessesCWE-327

Technical details

References

Community reviews

Related threats