Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-g7p5-89mh-248h | Lemur: Sub-CA creation never checks `AuthorityPermission` on the parent authority |
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
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-18T19:06:27.618Z
Reserved: 2026-08-05T18:14:42.064Z
Link: CVE-2026-71317
No data.
Status : Received
Published: 2026-08-18T20:17:23.910
Modified: 2026-08-18T20:17:23.910
Link: CVE-2026-71317
No data.
OpenCVE Enrichment
Updated: 2026-08-18T21:00:04Z
Github GHSA