Trusted certificate issuance via unchecked parent authority
Published Aug 18, 2026 · Updated Aug 19, 2026
Missing authorization in sub-CA creation in Netflix Lemur before 1.9.3 allows remote authenticated users to issue trusted certificates via an unauthorized parent authority. AssociatedAuthoritySchema resolves the caller-supplied parent with fetch_objects, and AuthoritiesList.post passed that object into authority creation without an AuthorityPermission check, allowing cryptography-issuer to sign a new intermediate with the parent authority_certificate.private_key. Exploitation requires an authenticated non-read-only account and the supported configuration with ADMIN_ONLY_AUTHORITY_CREATION disabled; the resulting intermediate can mint certificates under an internal root for which the caller holds no role, and its private key can be used outside Lemur.
Summary
What happened
Missing authorization in sub-CA creation in Netflix Lemur before 1.9.3 allows remote authenticated users to issue trusted certificates via an unauthorized parent authority. AssociatedAuthoritySchema resolves the caller-supplied parent with fetch_objects, and AuthoritiesList.post passed that object into authority creation without an AuthorityPermission check, allowing cryptography-issuer to sign a new intermediate with the parent authority_certificate.private_key. Exploitation requires an authenticated non-read-only account and the supported configuration with ADMIN_ONLY_AUTHORITY_CREATION disabled; the resulting intermediate can mint certificates under an internal root for which the caller holds no role, and its private key can be used outside Lemur.
The record
- CVE
- CVE-2026-71317
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- Netflix
- Product
- Lemur
- Classifications
- CWE-862, T1649
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.9.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-g7p5-89mh-248h proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo