Description
Lemur manages TLS certificate creation. Prior to 1.9.2, lemur/certificates/verify.py accepted CRL Distribution Point and OCSP responder URLs from uploaded certificate extensions and used them in crl_verify and ocsp_verify without adequate destination validation. An authenticated operator could submit a certificate through POST /api/1/certificates/upload and cause verify_string to reach loopback, RFC1918, link-local, or instance-metadata destinations such as 169.254.169.254. The requests could probe internal services and create side effects from the Lemur host network position. The CRL path also used an unbounded cache, allowing attacker-controlled entries to persist and consume memory. The fix validates destinations, supports explicit trusted-host allowlists, and bounds the CRL cache. This issue is fixed in version 1.9.2.
Published: 2026-08-18
Score: 6.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

An authenticated operator can upload a certificate that contains attacker‑controlled CRL Distribution Point or OCSP responder URLs. Lemur will use those URLs during certificate verification without proper destination validation, allowing the service to perform HTTP requests to arbitrary internal addresses, including RFC1918, link‑local, or instance‑metadata endpoints such as 169.254.169.254. This can result in internal network probing, side‑effects on services reachable from the Lemur host, and memory consumption from an unbounded CRL cache. The weakness is a Server Side Request Forgery (SSRF) flaw that can be exploited after authentication. The CVE is identified as CWE‑918.

Affected Systems

The affected product is Netflix Lemur, versions prior to 1.9.2. Operators using the upload API (POST /api/1/certificates/upload) on these versions are vulnerable.

Risk and Exploitability

The CVSS score of 6.3 indicates a moderate risk. No EPSS score is available and the vulnerability is not listed in the CISA KEV catalog. Because the vulnerability requires authentication, a legitimate user with operator privileges could trigger the SSRF. An attacker lacking such privileges would need to compromise an account or gain access through other means. The vulnerability does not allow arbitrary code execution but permits internal network reconnaissance and potential side‑effect attacks from the Lemur host.

Generated by OpenCVE AI on August 18, 2026 at 20:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Lemur to version 1.9.2 or later, which validates RFC‑approved destinations and bounds the CRL cache.
  • Configure the trusted‑host allowlist to restrict permitted CRL and OCSP URLs, ensuring only known, safe endpoints are used.
  • Monitor application logs for certificate verification requests to detect any abnormal outbound traffic or repeated failed verifies.

Generated by OpenCVE AI on August 18, 2026 at 20:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-54vg-pfh7-jq95 Lemur: Crafted CRL/OCSP URLs in uploaded certificates lead to post-authentication SSRF
History

Tue, 18 Aug 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Netflix
Netflix lemur
Vendors & Products Netflix
Netflix lemur

Tue, 18 Aug 2026 19:00:00 +0000

Type Values Removed Values Added
Description Lemur manages TLS certificate creation. Prior to 1.9.2, lemur/certificates/verify.py accepted CRL Distribution Point and OCSP responder URLs from uploaded certificate extensions and used them in crl_verify and ocsp_verify without adequate destination validation. An authenticated operator could submit a certificate through POST /api/1/certificates/upload and cause verify_string to reach loopback, RFC1918, link-local, or instance-metadata destinations such as 169.254.169.254. The requests could probe internal services and create side effects from the Lemur host network position. The CRL path also used an unbounded cache, allowing attacker-controlled entries to persist and consume memory. The fix validates destinations, supports explicit trusted-host allowlists, and bounds the CRL cache. This issue is fixed in version 1.9.2.
Title Lemur: Post-authentication SSRF via certificate verification - attacker-controlled CRL and OCSP URLs in uploaded certificates
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-19T15:15:42.749Z

Reserved: 2026-06-16T15:13:28.165Z

Link: CVE-2026-55162

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-18T19:16:58.217

Modified: 2026-08-19T16:17:57.283

Link: CVE-2026-55162

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T20:45:04Z

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)