CVE-2026-71317 Netflix CVE debrief

Who should care

Defenders who manage Lemur deployments should assess their exposure and verify their version. They should also review user roles and permissions to prevent unauthorized certificate creation.

Why it matters

CVE-2026-71317 is a vulnerability in Lemur's TLS certificate creation process. Prior to version 1.9.3, an authenticated non-read-only user could create a sub-CA chained to an internal root without proper permissions, allowing them to issue trusted certificates and use the private key outside of Lemur. Defenders should prioritize verifying their Lemur deployment's version and ensuring it is updated to 1.9.3 or later. They should also review their current user roles and permissions to prevent unauthorized certificate creation.

• An authenticated non-read-only user could issue trusted certificates
• The private key of the intermediate could be used outside Lemur
• Bypassing normal issuance controls
• Verification of Lemur deployment version and user permissions is required

Technical summary

The vulnerability was in Lemur's TLS certificate creation process. Prior to version 1.9.3, an authenticated non-read-only user could create a sub-CA chained to an internal root without proper permissions. This was possible because the POST /api/1/authorities with type=subca did not require AuthorityPermission on the parent authority when ADMIN_ONLY_AUTHORITY_CREATION was false. The fix checks AuthorityPermission on every supplied parent before invoking the issuer, which uses the parent authority_certificate.private_key to sign a new intermediate.

Defensive priority

Defenders should prioritize verifying their Lemur deployment's version and ensuring it is updated to 1.9.3 or later. They should also review their current user roles and permissions to prevent unauthorized certificate creation.

Recommended defensive actions

• Verify Lemur deployment version and update to 1.9.3 or later
• Review current user roles and permissions to prevent unauthorized certificate creation
• Monitor for suspicious certificate issuance activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability was fixed in version 1.9.3 of Lemur. The issue allowed an authenticated non-read-only user to create a sub-CA chained to an internal root without proper permissions. This was possible because the POST /api/1/authorities with type=subca did not require AuthorityPermission on the parent authority when ADMIN_ONLY_AUTHORITY_CREATION was false. The fix checks AuthorityPermission on every supplied parent before invoking the issuer. Evidence is limited to public statements from the vendor and CVE Program records.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.