Advisory

PYSEC-2026-3678

Details, part 2 of 2. The advisory

Details

Source artifact: audit/harnesses/public-repo-threat-model-harness/results/netflix-lemur-100run-mythos-20260627T051129Z/findings.jsonl (run_050, finding cluster lemur-revoke-via-duplicate, 2/100 runs).

Suggested fix

Decouple CA-side revocation authority from Lemur row ownership:

  1. On POST /certificates/upload, if authority is supplied enforce AuthorityPermission for that authority, and reject/ignore caller-supplied external_id.
  2. Before calling plugin.revoke_certificate, look up all Certificate rows sharing the same (authority_id, serial) or body and require CertificatePermission on every match (and run the endpoint-attached check against all matches).
  3. Consider a DB uniqueness constraint or dedup on (authority_id, serial) so a second row for the same CA-issued certificate cannot be created.
  4. Stop exposing external_id in CertificateOutputSchema to non-owners.

Sources & licences