← SSL.com cases
Bugzilla #2076197 Ca Certificate Compliance Self Reported Incident Ccadb Disclosure Issue Incident Opened By Ca

SSL.com CCADB CRL URL disclosure mismatch and follow-up corrections

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 that a CRL URL disclosed in CCADB for the subordinate CA Euronet TLS Issuing RSA CA 1 did not exactly match the CRL URL in certificates issued by that CA. The mismatch was a one-character hostname typo in the CCADB record, while the certificate’s CRL Distribution Points extension contained the correct URL. SSL.com corrected the CCADB record the same day it was identified, and later found additional CA records with incorrect CRL disclosures after running a validation job. The full incident report says the affected CCADB disclosures for all listed CAs were corrected, and that relying parties were not affected because the certificates contained the correct CRL URL and the CRL was available. SSL.com also posted action items to improve disclosure review and automated mismatch checking, with follow-up updates still pending.

Model: gpt-5.4-mini Generated: 2026-10-20 17:46 UTC Confidence: 0.97 4 comments
Chronology
  1. Earliest affected CA record date identified in the incident timeline.
  2. SSL.com received a CPR reporting a CCADB CRL URL mismatch for Euronet TLS Issuing RSA CA 1 and corrected the CCADB record the same day.
  3. A validation job found six additional CA records with mismatched CRL disclosures.
  4. SSL.com corrected the CCADB CRL disclosures for the six additional CAs.
  5. A later validation run found six more CAs with incorrect CRL disclosures, and SSL.com corrected them.
  6. SSL.com posted the full incident report.
  7. SSL.com said action items 1 and 2 were complete and requested the next update date be set to 2026-11-15.
Thread Activity
  1. SSL.com — SSL.com posted a preliminary incident report describing the CCADB CRL URL mismatch and stating the source was a third-party report.
  2. SSL.com — SSL.com posted the full incident report, including the timeline, impact, and corrective actions.
  3. SSL.com — SSL.com said action items #1 and #2 were complete, action items #3 and #4 were in progress, and asked for the next update date to be set to 2026-11-15.
Participants
SSL.com
Related Bugzilla IDs Mentioned
Similar Local Cases
#2077599 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Revocation Issue Opened 2026-10-02 Still Open · 89% similar
SSL.com: Inconsistent published CRL for one ICA
#2071491 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Validation Issue Opened 2026-09-11 Still Open · 89% 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 · 86% similar
SSL.com: Test websites for EV enabled Roots with non-EV certificates
#1927532 RESOLVED Incident Opened 2024-10-28 · Closed 2025-08-26 · 78% similar
SSL.com: Issuance of certificates using keys previously reported as compromised
#1931636 RESOLVED Incident Opened 2024-11-15 · Closed 2025-02-12 · 78% similar
SSL.com: Delay in publishing OCSP responses
#1579509 RESOLVED Incident Opened 2019-09-06 · Closed 2022-11-14 · 77% similar
SSL.com: Precertificates without corresponding certificates return OCSP value of "Unknown"
#1750631 RESOLVED Incident Revocation Issue Opened 2022-01-17 · Closed 2024-06-30 · 77% 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 · 77% similar
SSL.com: Issuance of 1 EV TLS certificate using a Registration/Incorporation Agency not included in our approved public list.

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

⚠

Confirm action