← Actalis cases
Bugzilla #2077464 Ca Certificate Compliance Incident Self Reported Incident Delayed Revocation Problem Reporting Failure

Actalis: Root CA CRLs were not republished within 24 hours after SubCA revocations

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

Actalis reported that its Root CA CRLs were not regenerated and published within the required 24 hours after several SubCA revocations. The issue involved three TLS SubCA certificates and one S/MIME SubCA certificate that were revoked on 2026-08-04 after internal verification procedures detected technical defects. The corresponding CRLs were not updated until the scheduled quarterly publication on 2026-09-29, about 56 days later. Actalis said the problem was identified first by an external report for the TLS case and then by internal checks for the S/MIME case. The bug remains assigned, and the thread indicates Actalis provided a preliminary incident report, a weekly update, and then a full incident report describing the non-compliance and its timeline.

Model: gpt-5.4-mini Generated: 2026-10-20 17:32 UTC Confidence: 0.96 3 comments
Chronology
  1. Actalis revoked three TLS SubCA certificates and one S/MIME SubCA certificate after internal verification procedures detected technical defects.
  2. The 24-hour CRL publication deadlines elapsed without the corresponding Root CA CRLs being regenerated and published.
  3. Actalis published CRL number 7 for the TLS and S/MIME roots, including the revocation entries.
  4. Actalis received an external report about the delayed CRL publication for the TLS root.
Thread Activity
  1. Staff representative — Actalis filed a preliminary incident report saying an external report had identified delayed publication of revocation information in the CRL and that a full incident report would follow.
  2. Staff representative — Actalis said it was continuing its internal investigation and would publish the full incident report within the required timeframe.
  3. Staff representative — Actalis filed the full incident report explaining that the CRLs were not regenerated and published within 24 hours after the revocations.
Participants
Staff representative
External References
Similar Local Cases
#2056934 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-07-22 · Closed 2026-10-05 · 89% similar
Actalis: failure to timely update CP/CPS for AgID SubCAs
#2081712 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Delayed Revocation Opened 2026-10-14 Still Open · 74% similar
DigiCert: Publishing timeline for CRL
#2077611 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Revocation Issue Opened 2026-10-02 Still Open · 74% similar
GoDaddy: Delayed CRL Updates
#2077068 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Revocation Issue Opened 2026-10-01 Still Open · 74% similar
Telekom Security: Failure in automatic issuance of CRLs
#2076163 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-09-28 Still Open · 74% similar
Telekom Security: Failure to respond to a certificate problem report within 24 hours
#2080698 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Ccadb Disclosure Issue Opened 2026-10-12 Still Open · 74% similar
Certigna: Failure to announce completion of action item within prescribed time period
#2076201 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Revocation Issue Opened 2026-09-28 Still Open · 72% similar
IZENPE: revocation reason code not included in CRL issued by Root
#2080806 ASSIGNED Ca Certificate Compliance Externally Reported Incident Incident Vulnerability Disclosure Opened 2026-10-12 Still Open · 72% similar
Actalis: Non-compliant OCSP responses and OCSP responder certificate

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

⚠

Confirm action