Authenticated certificate export via misplaced ownership check
Published Aug 18, 2026 · Updated Aug 19, 2026
Authorization bypass in Netflix Lemur before 1.9.3 allows remote authenticated users to export certificates via POST /api/1/certificates//export. In CertificateExport in lemur/certificates/views.py, the CertificatePermission ownership check sits inside the plugin.requires_key branch, so a plugin that declares requires_key false reaches plugin.export on another user's certificate without any ownership test while still receiving cert.private_key. With the bundled JavaTruststoreExportPlugin, the current effect is unauthorized export of public certificate body and chain plus false key_view audit entries; private-key disclosure becomes reachable if another requires_key false export plugin consumes the supplied key.
Summary
What happened
Authorization bypass in Netflix Lemur before 1.9.3 allows remote authenticated users to export certificates via POST /api/1/certificates//export. In CertificateExport in lemur/certificates/views.py, the CertificatePermission ownership check sits inside the plugin.requires_key branch, so a plugin that declares requires_key false reaches plugin.export on another user's certificate without any ownership test while still receiving cert.private_key. With the bundled JavaTruststoreExportPlugin, the current effect is unauthorized export of public certificate body and chain plus false key_view audit entries; private-key disclosure becomes reachable if another requires_key false export plugin consumes the supplied key.
The record
- CVE
- CVE-2026-71322
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- Netflix
- Product
- Lemur
- Classifications
- CWE-862
- Attack vector
- network
- 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
No public exploit references are available in this record.
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