← Sectigo cases
Bugzilla #2069640
Ca Certificate Compliance
Self Reported Incident
Incident
Opened By Ca
Single Ca Owner
Sectigo preliminary incident report on certificates not revoked after CP/CPS language issue
NEW
Sectigo
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update.
Always refer to the official Bugzilla thread as the authoritative source.
If you spot an inaccuracy, let me know via the contact form.
AI Summary
Sectigo opened this bug as a preliminary incident report and stated that it is self-reporting the issue. The report says the case follows discussion in bug 2061902 and that Sectigo opened bug 2069636 in connection with the underlying matter. Sectigo said it decided not to revoke certificates in connection with bug 2069636 and is using this bug to track the remaining validity of the affected corpus of certificates. The comment says a full incident report is being drafted and will include the reasons for the non-revocation decision. The bug is still NEW and no further resolution is recorded in the thread.
Chronology
- Sectigo opened a preliminary incident report about certificates it decided not to revoke in connection with bug 2069636.
Thread Activity
- Sectigo — Sectigo filed a preliminary incident report, identified the disclosure as self-reported, and said a full incident report is being drafted.
Participants
Sectigo
External References
Similar Local Cases
Sectigo: Incorrect JOI for federal credit unions
Sectigo: CP/CPS language involving extendedKeyUsage found to be subject to multiple interpretations
Sectigo: Failure to provide timely incident reports
Sectigo: Delay in some OCSP response signing due to application restart loop
Sectigo: Subject field with unvalidated information included in certificates
Sectigo: Failure to block disallowed LDH labels in domain names
Sectigo: CPR response issues
Sectigo: Incorrect jurisdictionStateOrProvinceName attribute value in Code Signing certificate