Certificate substitution via unchecked replacement references
Published Aug 18, 2026 · Updated Aug 18, 2026
Missing authorization in certificate replacement handling in Netflix Lemur before 1.9.3 allows remote authenticated users to substitute certificates. AssociatedCertificateSchema resolves replaces and replacements identifiers to Certificate objects with fetch_objects, and the create, upload, and edit paths assign them to Certificate.replaces without enforcing CertificatePermission on each referenced certificate. Any non-read-only account can therefore target certificates outside its ownership or roles, silence expiration notifications, and let certificate_rotate push the attacker certificate to endpoints that served the victim certificate, causing TLS disruption or unauthorized substitution.
Summary
What happened
Missing authorization in certificate replacement handling in Netflix Lemur before 1.9.3 allows remote authenticated users to substitute certificates. AssociatedCertificateSchema resolves replaces and replacements identifiers to Certificate objects with fetch_objects, and the create, upload, and edit paths assign them to Certificate.replaces without enforcing CertificatePermission on each referenced certificate. Any non-read-only account can therefore target certificates outside its ownership or roles, silence expiration notifications, and let certificate_rotate push the attacker certificate to endpoints that served the victim certificate, causing TLS disruption or unauthorized substitution.
The record
- CVE
- CVE-2026-71308
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Netflix
- Product
- Lemur
- Classifications
- CWE-862, CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 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=>= 0.5.0, < 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-cfh6-pv5c-38jv 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