Lemur manages TLS certificate creation. From 0.5.0 until 1.9.3, certificate create, upload, and edit requests accepted replaces[] or replacements identifiers that AssociatedCertificateSchema resolved with fetch_objects without a CertificatePermission check. Assigning those objects to Certificate.replaces invoked an append listener that disabled the victim certificate notifications and marked it as replaced. The victim was then excluded from get_all_pending_reissue, and certificate_rotate could deploy the attacker certificate to endpoints serving the victim. An authenticated non-read-only user could target certificates for which the user had no ownership or role, suppress lifecycle automation, and cause fleet-wide TLS disruption or unauthorized substitution. The fix authorizes every referenced replacement certificate before mutation. This issue is fixed in version 1.9.3.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-639",
"CWE-862"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/71xxx/CVE-2026-71308.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "0.5.0"
},
{
"fixed": "1.9.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "286874535160952143b0afe2d356642669f9d4c6"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v1.9.3",
"range": [
{
"fixed": "726506d15a6da8d9bcf5c39b4dc0c95535cf03c0"
}
],
"source": "REFERENCES_TAG"
}
]
}