Vulnerability Description
Lemur manages TLS certificate creation. Prior to 1.9.2, lemur.users.service.update assigned a replacement password directly to users.password, while lemur/users/models.py registered User.hash_password only for the before_insert event. Because no before_update listener ran, administrator-initiated password changes through PUT /api/1/users/ were committed as plaintext. The affected user could no longer authenticate normally because bcrypt verification received an unhashed value. A database, backup, replica, query-log, or administrative read compromise exposed immediately usable credentials without offline cracking. The fix registers hashing for before_update and avoids rehashing values that already have a bcrypt prefix. This issue is fixed in version 1.9.2.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/Netflix/lemur/commit/221c6d7275ac667bb8898ab48d2b96926a89c1c4
- https://github.com/Netflix/lemur/releases/tag/v1.9.2
- https://github.com/Netflix/lemur/security/advisories/GHSA-q437-g7fv-2jvv
- https://github.com/Netflix/lemur/security/advisories/GHSA-q437-g7fv-2jvv
FAQ
What is CVE-2026-55164?
CVE-2026-55164 is a vulnerability with a CVSS score of 4.9 (MEDIUM). Lemur manages TLS certificate creation. Prior to 1.9.2, lemur.users.service.update assigned a replacement password directly to users.password, while lemur/users/models.py registered User.hash_password...
How severe is CVE-2026-55164?
CVE-2026-55164 has been rated MEDIUM with a CVSS base score of 4.9/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-55164?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.