← Actalis cases
Bugzilla #2075655 Ca Certificate Compliance Incident Self Reported Incident Revocation Issue Repository Issue

Actalis: Incorrect revocation dates in CRL entries

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 a CRL issued by Actalis Domain Validation Server CA G3 contained incorrect revocationDate values for 149 revoked certificates. The issue was first identified after a third-party report on 2026-09-23, and Actalis said the affected CRL was reissued with corrected dates on 2026-09-25. Actalis stated that the underlying certificate records contained inconsistent date values and that other CRLs were reviewed with no similar issue found. The full incident report says the problem began with CRL no. 9196 published on 2026-08-06 and persisted until the corrected CRL was published. The thread remains open with weekly updates, and Actalis said progress is aligned with scheduled action items.

Model: gpt-5.4-mini Generated: 2026-10-20 17:32 UTC Confidence: 0.97 4 comments
Chronology
  1. Actalis published a CRL for Actalis Domain Validation Server CA G3 that contained incorrect revocationDate values for 149 revoked certificates.
  2. A third party reported that CRL number 10337 showed 149 entries with revocationDate encoded as 1970-01-21.
  3. Actalis corrected the affected records and reissued the CRL with the anomalous revocation dates fixed.
Thread Activity
  1. Staff representative — Actalis filed a preliminary incident report describing the incorrect revocation dates, the third-party report, and the reissued CRL.
  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, including the timeline, impact, and corrective actions.
  4. Staff representative — Actalis posted a weekly update saying progress was aligned with scheduled action items.
Participants
Staff representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2067210 ASSIGNED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Validation Issue Opened 2026-08-27 Still Open · 94% similar
Actalis: Incorrect CRL Distribution Point in TLS Server Certificates
#2012157 RESOLVED Self Reported Incident Revocation Issue Security Incident Opened 2026-01-23 · Closed 2026-03-08 · 82% similar
Actalis: Issuance of certificate using keys previously reported as compromised
#1824319 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2023-03-24 · Closed 2023-07-20 · 79% similar
Actalis: pre-certificates with “certificateHold” as the revocation reason
#1973238 RESOLVED Self Reported Incident Policy Document Issue Opened 2025-06-20 · Closed 2025-09-24 · 78% similar
Actalis: incorrect CP/S Last Update date in CCADB
#1982646 RESOLVED Self Reported Incident Opened 2025-08-12 · Closed 2025-12-01 · 78% similar
Actalis: missing CCADB disclosure for new SubCA
#2081113 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-10-13 Still Open · 73% similar
NAVER Cloud Trust Services: Cross-certificate with incorrect accessMethod (id-ad-ocsp instead of id-ad-caIssuers) in AIA
#2060581 ASSIGNED Ca Certificate Compliance Certificate Misissuance Self Reported Incident Incident Opened 2026-08-04 Still Open · 73% similar
Actalis: Issuance of Server TLS Certificates with id-kp-clientAuth against CPS
#2057448 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Delayed Revocation Opened 2026-07-24 · Closed 2026-10-02 · 73% similar
SwissSign: Invalid Entry in State field

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

⚠

Confirm action