CVE-2025-61152: python-jose thru 3.3.0 allows JWT tokens with 'alg=none' to be decoded and accepted without any
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 19 Nov 2026, 02:14 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 2026.
What to do
AI-suggested
Developers should explicitly reject JWT tokens with the 'alg=none' algorithm during token validation to mitigate this vulnerability. Until an official fix is released, applications must implement this check to prevent acceptance of unsigned tokens.
Description
python-jose versions through 3.3.0 allow JWT tokens with the 'alg=none' header to be decoded and accepted without cryptographic signature verification. This vulnerability enables attackers to craft forged tokens with arbitrary claims, such as elevated privileges, bypassing authentication checks in applications relying on python-jose for token validation.
References
- nvd.nist.gov/vuln/detail/CVE-2025-61152 (opens in a new tab)
- github.com/mpdavis/python-jose/issues/391 (opens in a new tab)
- github.com/javiermorales36/PoC-for-python-jose-alg-none-JWT-bypass-vulnerability/blob/main/CVE-2025-61152_Security_Advisory.md (opens in a new tab)
- pypi.org/project/python-jose (opens in a new tab)