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.2%, top 92% 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
Trending — 3 sources updated this weekElevated
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%CVSS: 8.1Exploit: 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. 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.1(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 18, 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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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-08-21 04:53 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-19 18:57 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 07:39 UTCEG score recompute
  6. 2026-08-18 20:22 UTCEG score recompute
  7. 2026-08-18 19:45 UTCEG score recompute
  8. 2026-08-18 19:19 UTCEG score recompute
  9. 2026-08-18 19:18 UTCMITRE cvelistV5first tracked

Related CVEs(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 in the National Vulnerability Database on August 18, 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% probability of exploitation in the next 30 days, which ranks it in the top 92.3% of all scored CVEs.
What is the CVSS score of CVE-2026-71308?
CVE-2026-71308 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-71308?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71308, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs