CVE-2026-55166

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.9Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Lemur manages TLS certificate creation. Prior to 1.9.2, authenticated users could influence an ACME authority acme_url without an effective server-side destination restriction and trigger AcmeHandler.setup_acme_client to make backend requests. An attacker could target cloud instance metadata or internal services from Lemur network context, potentially obtaining credentials available to the host. The advisory also identifies creator-equality authorization behavior that could preserve access to certificate key material after ownership or role changes, with insufficient export_private_key audit context to distinguish that access path. Together, the acme_url server-side request forgery and authorization weakness could expose cloud credentials and long-lived PKI private-key access. The fix adds ACME_DIRECTORY_HOST_ALLOWLIST validation and enriches key-export audit events with creator and current-owner context. This issue is fixed in version 1.9.2.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

Published

June 25, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Oct 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

Lemur 1.9.0: any SSO-authenticated user achieves AWS IAM compromise and permanent PKI key access via ACME acme_url SSRF and creator-equality IDOR · Advisory · Netflix/lemur · GitHub

https://github.com/Netflix/lemur/security/advisories/GHSA-v2wp-frmc-5q3v
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 872f6e282542 (Netflix/lemur)

Patch available: Netflix/lemur v1.9.2 (contains commit 872f6e282542)

https://github.com/Netflix/lemur/commit/872f6e282542352f2bf3f6e2bcc504ab81e1843d

Vendor Advisories for CVE-2026-55166(1)

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

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(3)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 15:22 UTCEPSS rescore
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-23 08:25 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 07:19 UTCEG score recompute
  22. 2026-09-17 19:31 UTCEPSS rescore
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-15 03:11 UTCEPSS rescore
Show 39 more
  1. 2026-09-14 01:16 UTCEG score recompute
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:41 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-08 22:59 UTCEG score recompute
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-30 19:28 UTCEG score recompute
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 23:16 UTCEG score recompute
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 21:50 UTCEG score recompute
  23. 2026-08-24 13:08 UTCEG score recompute
  24. 2026-08-23 02:25 UTCEG score recompute
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-22 01:28 UTCEG score recompute
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-20 23:59 UTCEG score recompute
  29. 2026-08-20 22:55 UTCEPSS rescore
  30. 2026-08-20 07:01 UTCEG score recompute
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-19 01:13 UTCEG score recompute
  33. 2026-08-18 20:25 UTCEG score recompute
  34. 2026-08-18 19:45 UTCEG score recompute
  35. 2026-08-18 19:25 UTCEG score recompute
  36. 2026-07-30 13:58 UTCEG score recompute
  37. 2026-07-26 14:54 UTCEG score recompute
  38. 2026-07-23 03:20 UTCEG score recompute
  39. 2026-06-25 22:46 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55166?
CVE-2026-55166 is a critical vulnerability published on June 25, 2026. Lemur manages TLS certificate creation. Prior to 1.9.2, authenticated users could influence an ACME authority acmeurl without an effective server-side destination restriction and trigger AcmeHandler.setupacmeclient to make backend requests. An attacker could target cloud instance metadata or…
When was CVE-2026-55166 disclosed?
CVE-2026-55166 was first published on June 25, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55166 actively exploited?
CVE-2026-55166 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55166?
CVE-2026-55166 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55166?
A fix for CVE-2026-55166 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55166 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-55166

Explore →

Is Your Infrastructure Affected by CVE-2026-55166?

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

Book a Demo →Browse All CVEs