CVE-2026-55164

MEDIUMPre-NVD 4.94.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.9 from GitHub Security Advisory (severity: MODERATE) published 2026-06-25. A secondary CVSS source baseline 4.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-61150 (ENISA EUVD) · GHSA-q437-g7fv-2jvv (GitHub Security Advisories) · PYSEC-2026-2587 (OSV.dev)Source: ENISA EUVD

4.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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 v3
4.9
EG Score
4.9MEDIUMmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity49% × 45%
Impact severity (EG Severity): CVSS 4.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.9): severity, escalated by confirmed exploitation. This CVE's 4.9 is its impact severity (EG Severity), not escalated.

EG Severity
4.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 25, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)

Plaintext password storage in Lemur user-update path · Advisory · Netflix/lemur · GitHub

https://github.com/Netflix/lemur/security/advisories/GHSA-q437-g7fv-2jvv
GitHub release Patch Available

v1.9.2

Patch available: Netflix/lemur v1.9.2

https://github.com/Netflix/lemur/releases/tag/v1.9.2
GitHub commit Patch Available

commit 221c6d7275ac (Netflix/lemur)

Patch available: Netflix/lemur v1.9.2 (contains commit 221c6d7275ac)

https://github.com/Netflix/lemur/commit/221c6d7275ac667bb8898ab48d2b96926a89c1c4

Vendor Advisories for CVE-2026-55164(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piplemur @ 1.9.2 (fixes <= 1.9.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
lemur0.11.0 ... 1.9.1 (19 versions)
  • every version up to 1.9.2: fixed in 1.9.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-q437-g7fv-2jvv · GitHub severity MODERATE · GitHub CVSS 4.9
  3. 2026-11-01 07:44 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-30 11:25 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-25 14:19 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-22 21:16 UTCEG score recompute
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-10-18 03:30 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 68 more
  1. 2026-10-13 22:54 UTCOSV refresh
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-12 15:56 UTCEG score recompute
  5. 2026-10-11 19:39 UTCEG score recompute
  6. 2026-10-11 16:54 UTCEG score recompute
  7. 2026-10-11 14:17 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  26. 2026-09-23 08:25 UTCEG score recompute
  27. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  28. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  29. 2026-09-18 07:19 UTCEG score recompute
  30. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  31. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-09-14 01:16 UTCEG score recompute
  35. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-09-12 15:41 UTCEG score recompute
  37. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-09-08 23:00 UTCEG score recompute
  39. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  40. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  42. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-08-30 19:28 UTCEG score recompute
  47. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-27 23:16 UTCEG score recompute
  51. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  54. 2026-08-24 13:42 UTCEG score recompute
  55. 2026-08-23 12:03 UTCEG score recompute
  56. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  57. 2026-08-22 10:25 UTCEG score recompute
  58. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-08-21 08:40 UTCEG score recompute
  60. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-08-20 07:01 UTCEG score recompute
  62. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  63. 2026-08-18 20:25 UTCEG score recompute
  64. 2026-08-18 19:20 UTCEG score recompute
  65. 2026-07-31 02:48 UTCEG score recompute
  66. 2026-07-26 14:54 UTCEG score recompute
  67. 2026-07-23 03:20 UTCEG score recompute
  68. 2026-06-25 22:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55164?
CVE-2026-55164 is a medium-severity vulnerability; its CVE record was published on June 25, 2026. 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…
When was the CVE record for CVE-2026-55164 published?
The CVE record for CVE-2026-55164 was published on June 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-55164 actively exploited?
CVE-2026-55164 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55164?
CVE-2026-55164 has a CVSS base score of 4.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55164?
A fix for CVE-2026-55164 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55164 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55164

Explore →

Is Your Infrastructure Affected by CVE-2026-55164?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.