CVE-2026-71303

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% 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
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: 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, _validate_acme_url enforced ACME_DIRECTORY_HOST_ALLOWLIST when an authority was created, but PUT /api/1/authorities/ passed options to lemur/authorities/service.py without applying the same check. A user holding an authority role could replace the stored acme_url with an internal service or instance-metadata URL such as 169.254.169.254. The next issuance operation loaded that value and passed it to ClientV2.get_directory, causing an outbound request from the Lemur backend. This bypassed the creation-time mitigation for CVE-2026-55166 and could expose internal services or cloud metadata. The fix revalidates acme_url whenever authority options are updated. This issue is fixed in version 1.9.3.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
51(Track)
EG Risk 51/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
Severity77% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
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, 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 edca0390f930 (Netflix/lemur)

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

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

Incomplete fix for GHSA-v2wp-frmc-5q3v -- ACME authority update endpoint allows non-admin to replace `acme_url` with internal IP, bypassing allowlist · Advisory · Netflix/lemur · GitHub

https://github.com/Netflix/lemur/security/advisories/GHSA-v5rc-cpwc-cfpr

Vendor Advisories for CVE-2026-71303(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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 02:43 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-19 18:14 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 07:14 UTCEG score recompute
  6. 2026-08-18 20:22 UTCEG score recompute
  7. 2026-08-18 19:53 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-71303?
CVE-2026-71303 is a high vulnerability published on August 18, 2026. Lemur manages TLS certificate creation. Prior to 1.9.3, validateacmeurl enforced ACMEDIRECTORYHOSTALLOWLIST when an authority was created, but PUT /api/1/authorities/ passed options to lemur/authorities/service.py without applying the same check. A user holding an authority role could replace the…
When was CVE-2026-71303 disclosed?
CVE-2026-71303 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-71303 actively exploited?
CVE-2026-71303 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 88.3% of all scored CVEs.
What is the CVSS score of CVE-2026-71303?
CVE-2026-71303 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-71303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71303, 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-71303

Explore →

Is Your Infrastructure Affected by CVE-2026-71303?

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

Start Free Scan →Browse All CVEs