Description
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.
Published: 2026-08-18
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw allows any authenticated user who is not read‑only, when ADMIN_ONLY_AUTHORITY_CREATION is set to false, to create a new sub‑CA under a parent authority without providing AuthorityPermission. The parent authority’s private key is then used by the backend issuer to sign the new intermediate, and the resulting key material may be extracted and used outside Lemur. This grants an attacker the ability to issue certificates trusted by clients that rely on the parent root, effectively bypassing all issuance controls and compromising the integrity of the certificate ecosystem.

Affected Systems

Netflix Lemur, versions prior to 1.9.3. The vulnerability is triggered by POST /api/1/authorities requests with type=subca. Users with any authenticated role that is not read‑only are affected in configurations where ADMIN_ONLY_AUTHORITY_CREATION is disabled.

Risk and Exploitability

With a CVSS score of 6.5 the risk is moderate but significant. EPSS data is not available, and the vulnerability is not listed in CISA KEV, indicating no known widespread exploitation. The likely attack vector is authenticated remote API usage; any user who can submit the creation request can chain a sub‑CA to an internal root, issuing certificates that clients will trust and giving the attacker a foothold for further attacks.

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

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Lemur to version 1.9.3 or later, where the fix validates AuthorityPermission on all supplied parent authorities.
  • If upgrading is delayed, set ADMIN_ONLY_AUTHORITY_CREATION to true to enforce permission checks on sub‑CA creation and prevent unauthorized chain building.
  • Restrict POST /api/1/authorities type=subca access to privileged users only and enable auditing of all sub‑CA creation requests.

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

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-g7p5-89mh-248h Lemur: Sub-CA creation never checks `AuthorityPermission` on the parent authority
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:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Lemur: Sub-CA creation never checks `AuthorityPermission` on the parent authority
Weaknesses CWE-862
References
Metrics cvssV3_1

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


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-18T19:06:27.618Z

Reserved: 2026-08-05T18:14:42.064Z

Link: CVE-2026-71317

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-18T20:17:23.910

Modified: 2026-08-18T20:17:23.910

Link: CVE-2026-71317

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T21:00:04Z

Weaknesses