← DigiCert cases
Bugzilla #2073668 Ca Certificate Compliance Incident Externally Reported Incident Revocation Issue Delayed Revocation

DigiCert delayed revocation of SHA-1 issuing CA certificates

ASSIGNED DigiCert
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

This case concerns DigiCert’s failure to revoke two subordinate CA certificates that still used SHA-1 signatures by the required deadline. A third party reported that DigiCert Grid Trust CA had not been revoked by 2026-09-15, and DigiCert later identified a second affected CA, DigiCert EV Code Signing CA. DigiCert said both CAs were not in active use and were revoked on 2026-09-18. DigiCert explained that the deadline was missed because its review of the relevant ballot requirements focused on active issuing hierarchies and did not identify these dormant CAs as in scope. The bug remains assigned to DigiCert, and DigiCert said it has completed two action items and requested a next update date for the final action item.

Model: gpt-5.4-mini Generated: 2026-10-20 17:38 UTC Confidence: 0.98 5 comments
Chronology
  1. DigiCert Grid Trust CA was issued.
  2. DigiCert EV Code Signing CA was issued.
  3. SC097 and SMC016 required sunset of remaining SHA-1 signatures in certificates and CRLs.
  4. The affected subordinate CA certificates were revoked.
Thread Activity
  1. DigiCert — DigiCert filed a preliminary incident report saying a third party reported missed revocation of a SHA-1 issuing CA, and that two affected CAs had now been revoked.
  2. DigiCert — DigiCert filed the full incident report, stating the revocation deadline was missed because the affected dormant CAs were not identified as in scope.
  3. DigiCert — DigiCert said it was still working on the action items and would provide an update on or shortly after 2026-10-07.
  4. DigiCert — DigiCert said action items #1 and #2 were completed and requested a next update date of 2026-11-30 for action item #3.
Participants
DigiCert
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#1483639 RESOLVED Revocation Issue Delayed Revocation Opened 2018-08-15 · Closed 2024-06-30 · 79% similar
DigiCert / ADACOM: published expired CRLs
#1896053 RESOLVED Delayed Revocation Opened 2024-05-10 · Closed 2025-07-16 · 78% similar
Digicert: Delayed Revocation for bug 1894560
#2073233 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Delayed Revocation Opened 2026-09-17 Still Open · 73% similar
FNMT: Delayed Revocation of SHA-1 Signed Subordinate CA Certificate
#2058294 RESOLVED Delayed Revocation Incident Self Reported Incident Revocation Issue Opened 2026-07-27 · Closed 2026-09-08 · 73% similar
SDAIA: Delayed Revocation related to Bugzilla #2056942
#2072600 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Delayed Revocation Opened 2026-09-16 Still Open · 72% similar
Firmaprofesional: Delayed revocation of SHA-1-signed AC Firmaprofesional - CA1
#1639801 RESOLVED Delayed Revocation Opened 2020-05-21 · Closed 2023-02-22 · 72% similar
DigiCert: Failure to revoke key-compromised certificates within 24 hours
#2072600 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Delayed Revocation Opened 2026-09-16 Still Open · 71% similar
Firmaprofesional: Delayed revocation of SHA-1-signed AC Firmaprofesional - CA1
#2064673 ASSIGNED Ca Certificate Compliance Delayed Revocation Incident Self Reported Incident Opened 2026-08-19 Still Open · 71% similar
ACCV: Delayed revocation related to Bugzilla #2061746

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

⚠

Confirm action