CVE-2026-70666

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (10th percentile of EPSS-scored CVEs). 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
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Lemur manages TLS certificate creation. Prior to 1.9.3, an authority-role member could update acme_url through PUT /api/1/authorities/ without revalidation and direct setup_acme_client_no_retry to an attacker-controlled ACME server. ACME directory and order responses contain newNonce, newOrder, authorizations, and finalize URLs chosen by that server. The Lemur ClientV2 followed those URLs without requiring their host to match the configured directory host, allowing JWS-signed requests to internal services or cloud metadata endpoints. The issue required an ACME authority and a user authorized for that authority, but did not require global administrator privileges. The fix revalidates updates and introduces _PinnedClientNetwork to enforce a single allowed host for the complete ACME flow. This issue is fixed in version 1.9.3.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

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
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
github_release Patch Available

v1.9.3

Patch available: Netflix/lemur v1.9.3

https://github.com/Netflix/lemur/releases/tag/v1.9.3
github_commit Patch Available

commit 6dcb19b6d600 (Netflix/lemur)

Patch available: Netflix/lemur v1.9.3 (contains commit 6dcb19b6d600)

https://github.com/Netflix/lemur/commit/6dcb19b6d6004e97796d6a0344b130b2ba57f050
github Patch Available🟡 PoC Available

Server-Side Request Forgery via the ACME client following server-controlled URLs · Advisory · Netflix/lemur · GitHub

https://github.com/Netflix/lemur/security/advisories/GHSA-xpmj-wjcp-6pww

Vendor Advisories for CVE-2026-70666(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.2 (20 versions)
  • every version up to 1.9.3: fixed in 1.9.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 50× 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-05 11:41 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-03 17:37 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 03:22 UTCEG score recompute
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 01:26 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 22:03 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-30 09:47 UTCEG score recompute
  12. 2026-09-28 21:55 UTCEG score recompute
  13. 2026-09-28 13:52 UTCEPSS rescore
  14. 2026-09-27 21:14 UTCEG score recompute
  15. 2026-09-27 13:48 UTCEPSS rescore
  16. 2026-09-27 07:54 UTCEG score recompute
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-24 16:04 UTCEG score recompute
  19. 2026-09-24 02:31 UTCEG score recompute
  20. 2026-09-23 17:54 UTCEPSS rescore
  21. 2026-09-23 01:59 UTCEG score recompute
  22. 2026-09-22 01:26 UTCEG score recompute
  23. 2026-09-21 21:09 UTCEPSS rescore
  24. 2026-09-21 00:54 UTCEG score recompute
  25. 2026-09-20 20:16 UTCEPSS rescore
Show 59 more
  1. 2026-09-19 23:31 UTCEG score recompute
  2. 2026-09-18 22:59 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 22:28 UTCEG score recompute
  5. 2026-09-16 21:56 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 03:54 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 03:20 UTCEG score recompute
  11. 2026-09-13 02:47 UTCEG score recompute
  12. 2026-09-12 15:02 UTCEPSS rescore
  13. 2026-09-12 02:15 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 13:58 UTCEG score recompute
  16. 2026-09-10 13:24 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 09:32 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 16:24 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-07 04:07 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-06 01:13 UTCEG score recompute
  25. 2026-09-05 15:31 UTCEPSS rescore
  26. 2026-09-05 00:06 UTCEG score recompute
  27. 2026-09-04 11:07 UTCEG score recompute
  28. 2026-09-04 05:07 UTCEPSS rescore
  29. 2026-09-02 22:12 UTCEG score recompute
  30. 2026-09-02 14:12 UTCEPSS rescore
  31. 2026-09-01 21:40 UTCEG score recompute
  32. 2026-09-01 13:54 UTCEPSS rescore
  33. 2026-09-01 09:25 UTCEG score recompute
  34. 2026-09-01 04:40 UTCEPSS rescore
  35. 2026-08-31 04:56 UTCEG score recompute
  36. 2026-08-30 19:17 UTCEPSS rescore
  37. 2026-08-30 04:24 UTCEG score recompute
  38. 2026-08-30 01:22 UTCEPSS rescore
  39. 2026-08-29 03:46 UTCEG score recompute
  40. 2026-08-28 21:42 UTCEPSS rescore
  41. 2026-08-27 23:41 UTCEG score recompute
  42. 2026-08-26 23:09 UTCEG score recompute
  43. 2026-08-26 14:47 UTCEPSS rescore
  44. 2026-08-25 22:36 UTCEG score recompute
  45. 2026-08-25 13:49 UTCEPSS rescore
  46. 2026-08-24 22:04 UTCEG score recompute
  47. 2026-08-24 09:48 UTCEG score recompute
  48. 2026-08-23 09:16 UTCEG score recompute
  49. 2026-08-23 00:19 UTCEPSS rescore
  50. 2026-08-22 08:44 UTCEG score recompute
  51. 2026-08-21 23:49 UTCEPSS rescore
  52. 2026-08-21 08:12 UTCEG score recompute
  53. 2026-08-20 22:56 UTCEPSS rescore
  54. 2026-08-19 19:21 UTCEG score recompute
  55. 2026-08-19 18:38 UTCEG score recompute
  56. 2026-08-19 17:04 UTCEPSS rescore
  57. 2026-08-18 20:22 UTCEG score recompute
  58. 2026-08-18 19:19 UTCEG score recompute
  59. 2026-08-18 19:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-70666?
CVE-2026-70666 is a high vulnerability published on August 18, 2026. Lemur manages TLS certificate creation. Prior to 1.9.3, an authority-role member could update acmeurl through PUT /api/1/authorities/ without revalidation and direct setupacmeclientnoretry to an attacker-controlled ACME server. ACME directory and order responses contain newNonce, newOrder,…
When was CVE-2026-70666 disclosed?
CVE-2026-70666 was first published on August 18, 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-70666 actively exploited?
CVE-2026-70666 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70666?
CVE-2026-70666 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-70666?
A fix for CVE-2026-70666 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70666 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-70666

Explore →

Is Your Infrastructure Affected by CVE-2026-70666?

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