CVE-2026-70667

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th 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
Elevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Lemur manages TLS certificate creation. Prior to 1.9.3, _validate_revocation_url in lemur/certificates/verify.py checked the original CRL or OCSP URL but the later request could reach a different destination. The CRL requests.get call followed HTTP redirects without validating each Location target, so a public attacker-controlled URL could redirect to loopback, RFC1918, link-local, or instance-metadata addresses. Validation and connection also performed separate DNS resolutions, creating a time-of-check time-of-use window for DNS rebinding on both CRL and OCSP paths. An operator uploading a certificate through POST /api/1/certificates/upload could therefore induce blind internal requests despite the earlier mitigation. The fix disables redirects and pins validated addresses while preserving the correct Host value. This issue is fixed in version 1.9.3.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/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
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack 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). 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 Patch Available🟡 PoC Available

SSRF protection in certificate revocation checking bypassable via HTTP redirects and DNS rebinding (incomplete fix for GHSA-54vg-pfh7-jq95) · Advisory · Netflix/lemur · GitHub

https://github.com/Netflix/lemur/security/advisories/GHSA-f3qq-49m6-rw8f
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 ed504a830f38 (Netflix/lemur)

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

https://github.com/Netflix/lemur/commit/ed504a830f38a83825b1570302e9f38d6553938a

Vendor Advisories for CVE-2026-70667(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(2)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-70667?
CVE-2026-70667 is a medium vulnerability published on August 18, 2026. Lemur manages TLS certificate creation. Prior to 1.9.3, validaterevocation_url in lemur/certificates/verify.py checked the original CRL or OCSP URL but the later request could reach a different destination. The CRL requests.get call followed HTTP redirects without validating each Location target,…
When was CVE-2026-70667 disclosed?
CVE-2026-70667 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-70667 actively exploited?
CVE-2026-70667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70667?
CVE-2026-70667 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-70667?
A fix for CVE-2026-70667 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70667 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-70667

Explore →

Is Your Infrastructure Affected by CVE-2026-70667?

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

Book a Demo →Browse All CVEs