CVE-2026-55165

The record

Lemur manages TLS certificate creation. Prior to 1.9.2, the JWT verifier in lemur/auth/service.py:130-137 used fetch_token_header to read header_data["alg"] from an unverified token and passed that attacker-controlled value to decode_with_multiple_secrets. PyJWT 2.x rejects alg=none with the configured key, so the flaw is a defense-in-depth gap rather than a direct authentication bypass in the shipped configuration. The unpinned algorithm can become exploitable after an asymmetric-signing migration through algorithm confusion, and it weakens algorithm-based anomaly detection because the token chooses the recorded value. A separate disclosure of LEMUR_TOKEN_SECRET would also permit forged HS256 tokens, although that disclosure is an independent prerequisite. The fix introduces the server-controlled LEMUR_TOKEN_ALGORITHMS allowlist and defaults it to HS256. This issue is fixed in version 1.9.2.

Affected packages

Related vulnerabilities

• CVE-2026-87947 Improper Verification of Cryptographic Signature vulnerability in Drupal SAML SSO… CWE-347
• CVE-2026-84918 Improper Verification of Cryptographic Signature vulnerability in Drupal Monobank payment… CWE-347
• CVE-2026-102271 PyJWT is a Python implementation of JSON Web Token standards. CWE-347
• CVE-2026-102272 PyJWT is a Python implementation of JSON Web Token standards. CWE-347
• CVE-2026-102273 PyJWT is a Python implementation of JSON Web Token standards. CWE-347
• CVE-2026-102268 PyJWT is a Python implementation of JSON Web Token standards. CWE-347
• CVE-2026-102266 PyJWT is a Python implementation of JSON Web Token standards. CWE-347
• CVE-2026-73784 A potential security vulnerability in HPE IceWall products could be exploited to tamper… CWE-347