CVE-2026-71308

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (22nd 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
8.1EG
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: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Lemur manages TLS certificate creation. From 0.5.0 until 1.9.3, certificate create, upload, and edit requests accepted replaces[] or replacements identifiers that AssociatedCertificateSchema resolved with fetch_objects without a CertificatePermission check. Assigning those objects to Certificate.replaces invoked an append listener that disabled the victim certificate notifications and marked it as replaced. The victim was then excluded from get_all_pending_reissue, and certificate_rotate could deploy the attacker certificate to endpoints serving the victim. An authenticated non-read-only user could target certificates for which the user had no ownership or role, suppress lifecycle automation, and cause fleet-wide TLS disruption or unauthorized substitution. The fix authorizes every referenced replacement certificate before mutation. This issue is fixed in version 1.9.3.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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
Severity81% × 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.3%
EPSS %ILE
22nd
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 286874535160 (Netflix/lemur)

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

https://github.com/Netflix/lemur/commit/286874535160952143b0afe2d356642669f9d4c6
github Patch Available🟡 PoC Available

Unchecked `replaces[]` lets any user silence notifications and hijack auto-rotation for arbitrary certificates · Advisory · Netflix/lemur · GitHub

https://github.com/Netflix/lemur/security/advisories/GHSA-cfh6-pv5c-38jv

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-71308?
CVE-2026-71308 is a high vulnerability published on August 18, 2026. Lemur manages TLS certificate creation. From 0.5.0 until 1.9.3, certificate create, upload, and edit requests accepted replaces[] or replacements identifiers that AssociatedCertificateSchema resolved with fetchobjects without a CertificatePermission check. Assigning those objects to…
When was CVE-2026-71308 disclosed?
CVE-2026-71308 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-71308 actively exploited?
CVE-2026-71308 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71308?
CVE-2026-71308 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71308?
A fix for CVE-2026-71308 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71308 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-71308

Explore →

Is Your Infrastructure Affected by CVE-2026-71308?

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

Book a Demo →Browse All CVEs