← SSL.com cases
Bugzilla #2077599 Ca Certificate Compliance Incident Self Reported Incident Revocation Issue Repository Issue

SSL.com incident: inconsistent published CRLs for one issuing CA

ASSIGNED SSL.com
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

SSL.com reported an incident affecting the published CRLs for one TLS issuing CA. The problem was that revoked certificate serial numbers were intermittently missing from, or duplicated within, some CRLs. SSL.com said the issue affected only CRLs for Cloudflare TLS Issuing ECC CA 3 and that OCSP responses remained correct throughout. The company stated that the issue was identified after a third-party report, then investigated, corrected, and redeployed. SSL.com posted a preliminary incident report on 2026-10-02 and later posted the full incident report on 2026-10-16. The thread also references Bug 2029230 as the mass revocation event that preceded the CRL inconsistency.

Model: gpt-5.4-mini Generated: 2026-10-20 17:46 UTC Confidence: 0.96 3 comments
Chronology
  1. SSL.com completed a mass revocation of 1.7 million certificates, including certificates issued by Cloudflare TLS Issuing ECC CA 3.
  2. The first CRL was published that dropped an unexpired revoked serial number.
  3. SSL.com received an email reporting a CRL entry missing or duplicated issue and began investigating.
  4. SSL.com generated and published a corrected CRL after deploying a configuration fix.
  5. SSL.com completed deployment on impacted and non-impacted servers and posted a preliminary incident report.
  6. SSL.com posted the full incident report.
Thread Activity
  1. SSL.com — SSL.com opened a preliminary incident report describing intermittent missing or duplicated revoked serial numbers in a published CRL and said a full report would follow.
  2. SSL.com — SSL.com posted the full incident report with the timeline, impact, and remediation details.
Participants
SSL.com
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#2071491 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Validation Issue Opened 2026-09-11 Still Open · 90% similar
SSL.com: MPIC not performed for specific DCV path
#2081961 ASSIGNED Ca Certificate Compliance Self Reported Incident Validation Issue Opened By Ca Opened 2026-10-14 Still Open · 89% similar
SSL.com: Test websites for EV enabled Roots with non-EV certificates
#2076197 ASSIGNED Ca Certificate Compliance Self Reported Incident Ccadb Disclosure Issue Incident Opened 2026-09-28 Still Open · 89% similar
SSL.com: CRL URL typo in CRL URL disclosed to CCADB
#1962809 RESOLVED Self Reported Incident Revocation Issue Opened 2025-04-25 · Closed 2025-07-28 · 88% similar
SSL.com: Expired certificate for a “Valid” Test Website
#1750631 RESOLVED Incident Revocation Issue Opened 2022-01-17 · Closed 2024-06-30 · 87% similar
SSL.com: Issuance of TLS certificates with domain validation methods prohibited by SC-45
#1790693 RESOLVED Self Reported Incident Revocation Issue Opened 2022-09-13 · Closed 2023-03-24 · 87% similar
SSL.com: Issuance of 1 EV TLS certificate using a Registration/Incorporation Agency not included in our approved public list.
#1938236 RESOLVED Incident Revocation Issue Opened 2024-12-18 · Closed 2025-02-28 · 87% similar
SSL.com: Failure to process CAA records from one SubCA
#2029230 RESOLVED Self Reported Incident Revocation Issue Opened 2026-04-03 · Closed 2026-05-28 · 87% similar
SSL.com: Incorrect Open MPIC Lambda implementation by EJBCA ACME Service

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

⚠

Confirm action