What’s Vulnerable › Vulnerabilities
CVE-2026-71317: Lemur: Sub-CA creation never checks `AuthorityPermission` on the parent authority
- Severity: medium (CVSS 6.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-08-18 · updated 2026-10-22
- Weakness: CWE-862
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.
Affected products
- Netflix lemur: before 1.9.3
References
- https://github.com/Netflix/lemur/commit/8669011203ca3dd89d9e39bab9ef6850eca723f9
- https://github.com/Netflix/lemur/releases/tag/v1.9.3
- https://github.com/Netflix/lemur/security/advisories/GHSA-g7p5-89mh-248h
- https://github.com/Netflix/lemur/security/advisories/GHSA-g7p5-89mh-248h
Get alerted when CVE-2026-71317 or the next vulnerability affects your stack