Netflix Lemur up to 1.9.1 Password Hashing lemur/users/models.py lemur.users.service.update missing encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 1.20- |
Summary
A vulnerability categorized as problematic has been discovered in Netflix Lemur up to 1.9.1. Impacted is the function lemur.users.service.update of the file lemur/users/models.py of the component Password Hashing. Executing a manipulation of the argument Password can lead to missing encryption.
The identification of this vulnerability is CVE-2026-55164. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability classified as problematic was found in Netflix Lemur up to 1.9.1. This vulnerability affects the function lemur.users.service.update of the file lemur/users/models.py of the component Password Hashing. The manipulation of the argument password with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-55164 since 06/16/2026. The exploitation appears to be difficult. The attack can be initiated remotely. Additional levels of successful authentication are needed for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1600.
Upgrading to version 1.9.2 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/Netflix/lemur/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.5
VulDB Base Score: 2.2
VulDB Temp Score: 2.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.9
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Missing encryptionCWE: CWE-311 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Lemur 1.9.2
Timeline
06/16/2026 CVE reserved08/18/2026 Advisory disclosed
08/18/2026 VulDB entry created
08/18/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-55164 (🔒)
GCVE (CVE): GCVE-0-2026-55164
GCVE (VulDB): GCVE-100-391924
Entry
Created: 08/18/2026 21:08Changes: 08/18/2026 21:08 (67)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.