Quick answers
- Is CVE-2026-55164 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55164 being exploited in the wild.
- How severe is CVE-2026-55164?
- Medium severity, with a CVSS score of 4.9, published 18 August 2026.
- Which products and versions are affected?
- lemur (PyPI) <= 1.9.1, ECOSYSTEM:introduced=0,fixed=1.9.2.
- Is there a fix for CVE-2026-55164?
- Yes. lemur (PyPI): upgrade to 1.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55164 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-55164?
- Check whether you run lemur (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- lemur (PyPI): upgrade to 1.9.2 or later
pip install "lemur>=1.9.2"
Technical details
A vulnerability exists in the `lemur.users.service.update()` function where new passwords assigned via the `PUT /api/1/users/<id>` endpoint are written directly to the database in plaintext. While the `User` model includes a bcrypt hashing routine, it is only registered to SQLAlchemy's `before_insert` event and not the `before_update` event. An authenticated attacker with administrative privileges can trigger this by updating a user profile, causing the `password` column to be updated without invoking `hash_password()`. This results in a defense-in-depth failure where database exfiltration (via SQLi, backups, or logs) reveals raw credentials. The issue is fixed in version 1.9.2 by adding the missing event listener.
Affected products
- Netflix Lemur <= 1.9.1
Identifiers
- CVE-2026-55164
- GHSA-q437-g7fv-2jvv
- PYSEC-2026-2587
Timeline
- 2026-06-10: disclosed: Initial report to Netflix/lemur
- 2026-06-25: advisory: GitHub Advisory published
- 2026-06-25: patched: Version 1.9.2 released