CVE-2026-71317

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Lemur manages TLS certificate creation. Prior to 1.9.3, POST /api/1/authorities with type=subca did not require AuthorityPermission on the parent authority when ADMIN_ONLY_AUTHORITY_CREATION was false. AssociatedAuthoritySchema resolved the caller-supplied parent and passed it through authority creation to cryptography-issuer, which used the parent authority_certificate.private_key to sign a new intermediate. Any authenticated non-read-only user in that supported configuration could chain a sub-CA to an internal root for which the user held no role. The resulting intermediate could issue trusted certificates and its private key could be used outside Lemur, bypassing normal issuance controls. The fix checks AuthorityPermission on every supplied parent before invoking the issuer. This issue is fixed in version 1.9.3.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

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, github_commit, github_release.
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 8669011203ca (Netflix/lemur)

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

https://github.com/Netflix/lemur/commit/8669011203ca3dd89d9e39bab9ef6850eca723f9
github Patch Available🟡 PoC Available

Sub-CA creation never checks `AuthorityPermission` on the parent authority · Advisory · Netflix/lemur · GitHub

https://github.com/Netflix/lemur/security/advisories/GHSA-g7p5-89mh-248h

Vendor Advisories for CVE-2026-71317(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 rangeFixed inDependents
lemur0.11.0 ... 1.9.2 (20 versions)1.9.3—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71317?
CVE-2026-71317 is a medium vulnerability published on August 18, 2026. Lemur manages TLS certificate creation. Prior to 1.9.3, POST /api/1/authorities with type=subca did not require AuthorityPermission on the parent authority when ADMINONLYAUTHORITYCREATION was false. AssociatedAuthoritySchema resolved the caller-supplied parent and passed it through authority…
When was CVE-2026-71317 disclosed?
CVE-2026-71317 was first published in the National Vulnerability Database 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-71317 actively exploited?
CVE-2026-71317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-71317?
CVE-2026-71317 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-71317?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71317, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-71317?

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

Start Free Scan →Browse All CVEs