CVE-2026-71417

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (below the 1st 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
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Lemur manages TLS certificate creation. Prior to 1.9.3, POST /api/1/certificates/upload allowed a non-read-only user to create a duplicate row using another certificate body, authority_id, serial, or external_id without requiring permission on the underlying authority. PUT /api/1/certificates//revoke authorized the caller against only the selected Lemur row, so the creator of the duplicate bypassed CertificatePermission. The duplicate had no cert.endpoints, which also bypassed the safeguard that prevents revocation of deployed certificates. Issuer plugins then revoked the real CA-side certificate using certificate.body or external_id under the stored authority credentials. An attacker could therefore revoke arbitrary managed certificates and cause fleet-wide TLS denial of service. The fix rejects duplicate authority_id and serial identities, requires authority access on upload, and checks every matching row during revocation. This issue is fixed in version 1.9.3.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
49
EG Risk 49/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
Severity73% × 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.1%
EPSS %ILE
below the 1st
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_commit, github_release, github.
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 851389ae737a (Netflix/lemur)

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

https://github.com/Netflix/lemur/commit/851389ae737a6d6bf16c1f9ca64a2ce56c1cc5c6
github Patch Available🟡 PoC Available

Any user can revoke arbitrary certificates at the CA by uploading a duplicate record and revoking it · Advisory · Netflix/lemur · GitHub

https://github.com/Netflix/lemur/security/advisories/GHSA-pxmc-2ffp-8j67

Vendor Advisories for CVE-2026-71417(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 8× in last 7d / 37× 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-03 17:37 UTCEG score recompute
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 17:56 UTCEPSS rescore
  4. 2026-10-02 01:25 UTCEG score recompute
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 22:40 UTCEG score recompute
  7. 2026-09-30 15:03 UTCEPSS rescore
  8. 2026-09-28 23:28 UTCEG score recompute
  9. 2026-09-27 21:14 UTCEG score recompute
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-27 07:54 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-25 01:25 UTCEG score recompute
  14. 2026-09-23 22:13 UTCEG score recompute
  15. 2026-09-23 17:54 UTCEPSS rescore
  16. 2026-09-22 20:24 UTCEG score recompute
  17. 2026-09-22 05:14 UTCEG score recompute
  18. 2026-09-21 21:09 UTCEPSS rescore
  19. 2026-09-21 03:25 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-20 01:26 UTCEG score recompute
  22. 2026-09-18 23:37 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-17 21:46 UTCEG score recompute
  25. 2026-09-16 15:05 UTCEG score recompute
Show 28 more
  1. 2026-09-16 14:08 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 11:25 UTCEG score recompute
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-13 19:57 UTCEG score recompute
  6. 2026-09-12 18:08 UTCEG score recompute
  7. 2026-09-12 15:02 UTCEPSS rescore
  8. 2026-09-11 16:15 UTCEG score recompute
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-10 14:08 UTCEG score recompute
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-05 19:06 UTCEG score recompute
  13. 2026-09-04 17:17 UTCEG score recompute
  14. 2026-09-04 05:07 UTCEPSS rescore
  15. 2026-08-29 03:46 UTCEG score recompute
  16. 2026-08-28 21:42 UTCEPSS rescore
  17. 2026-08-25 20:08 UTCEG score recompute
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 18:20 UTCEG score recompute
  20. 2026-08-21 00:01 UTCEG score recompute
  21. 2026-08-20 22:56 UTCEPSS rescore
  22. 2026-08-19 22:12 UTCEG score recompute
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 09:16 UTCEG score recompute
  25. 2026-08-18 20:22 UTCEG score recompute
  26. 2026-08-18 19:53 UTCEG score recompute
  27. 2026-08-18 19:19 UTCEG score recompute
  28. 2026-08-18 19:18 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-71417?
CVE-2026-71417 is a high vulnerability published on August 18, 2026. Lemur manages TLS certificate creation. Prior to 1.9.3, POST /api/1/certificates/upload allowed a non-read-only user to create a duplicate row using another certificate body, authorityid, serial, or externalid without requiring permission on the underlying authority. PUT /api/1/certificates//revoke…
When was CVE-2026-71417 disclosed?
CVE-2026-71417 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-71417 actively exploited?
CVE-2026-71417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71417?
CVE-2026-71417 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71417?
A fix for CVE-2026-71417 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71417 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-71417

Explore →

Is Your Infrastructure Affected by CVE-2026-71417?

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

Book a Demo →Browse All CVEs