Cyber Resilience

CVE-2024-53861

Pyjwt Project Pyjwt 2.10.0

Public PoC
Published
29 November 2024
Modified
22 September 2025
Patch / advisory
View advisory
CVSS Score v3.1 2.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0081 54th percentile
Risk Priority 24 floored blend · peak EPSS

Summary

CVE-2024-53861 is a low-severity Incorrect Comparison (CWE-697) vulnerability in Pyjwt Project Pyjwt. Its CVSS base score is 2.2 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Obfuscated Files or Information (T1027); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-25 (Reference Monitor) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

pyjwt is a JSON Web Token implementation in Python. An incorrect string comparison is run for `iss` checking, resulting in `"acb"` being accepted for `"_abc_"`. This is a bug introduced in version 2.10.0: checking the "iss" claim changed from `isinstance(issuer,…

more

list)` to `isinstance(issuer, Sequence)`. Since str is a Sequnce, but not a list, `in` is also used for string comparison. This results in `if "abc" not in "__abcd__":` being checked instead of `if "abc" != "__abc__":`. Signature checks are still present so real world impact is likely limited to denial of service scenarios. This issue has been patched in version 2.10.1. All users are advised to upgrade. There are no known workarounds for this vulnerability.

CWE(s)
CWE-697

Related Threats

MITRE ATT&CK Enterprise Techniques

T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-32597Same product: Pyjwt Project Pyjwt
CVE-2026-48526Same product: Pyjwt Project Pyjwt
CVE-2026-48524Same product: Pyjwt Project Pyjwt
CVE-2026-48522Same product: Pyjwt Project Pyjwt
CVE-2025-45768Same product: Pyjwt Project Pyjwt
CVE-2026-48523Same product: Pyjwt Project Pyjwt
CVE-2026-48525Same product: Pyjwt Project Pyjwt
CVE-2024-39534Shared CWE-697
CVE-2023-23766Shared CWE-697
CVE-2025-12192Shared CWE-697

Affected Assets

pyjwt project
pyjwt
2.10.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation directly exercises security-relevant comparisons to discover incorrect logic.

AC-25 Reference Monitor partial match

A reference monitor must be small and correct, structurally limiting the chance of flawed comparison logic in authorization decisions.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require correct implementation of comparison logic used for access and authentication decisions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly require correct logic for security comparisons and thereby prevent this class of flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect incorrect comparison flaws before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes code review and testing that can catch incorrect comparison logic.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate correct comparison logic for security decisions.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles can require robust comparison mechanisms for access decisions.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address avoiding incorrect comparison operators and logic.

A.8.5 Secure authentication partial match
degrades

Secure authentication mechanisms rely on correct comparison of credentials or tokens.

References