← Telia Company cases
Bugzilla #2075488 Ca Certificate Compliance Self Reported Incident Incident Policy Document Issue Remediation Tracking

Telia self-reported CRL signature algorithm non-conformance for EC issuer keys

UNCONFIRMED Telia Company
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

Telia reported a CRL signature algorithm non-conformance affecting several EC PKIs, after a third-party Certificate Problem Report was received on 2026-09-23. The issue was that CRLs for EC-384 issuer keys were signed with `ecdsaWithSHA256` and had an `AlgorithmIdentifier` `parameters` value of `NULL`, which Telia said violated RFC 5758 section 3.2 and related Baseline Requirements and CP/CPS requirements. Telia stated that the affected PKIs included Telia EC TLS Root CA v3, Telia EC TLS DV CA v4, Telia EC Email Root CA v3, Telia EC Client Root CA v3, and Telia EC Signing Root CA v3. Telia said the issue was identified in internal review after the CPR, remedial actions were completed, and updated CRLs were generated; it also said no certificates were affected. The thread shows Telia continuing to track action items, including amending CA ceremony documentation to explicitly verify CRL signature settings, with that item marked completed in the latest update.

Model: gpt-5.4-mini Generated: 2026-10-20 17:47 UTC Confidence: 0.96 4 comments
Chronology
  1. Affected self-signed root CAs were issued with incorrect CRL signature algorithm settings.
  2. A third-party Certificate Problem Report was received about the CRL issue.
  3. Telia posted a preliminary incident report in Bugzilla.
  4. Telia posted the full incident report with timeline, impact, and remediation details.
  5. Telia reported completion of the documentation update action item and said one open action item remained.
Thread Activity
  1. Teliacompany representative — Telia filed a preliminary incident report describing the CRL signature algorithm and `parameters`-field issue and said it would submit a full report later.
  2. Teliacompany representative — Telia said it had completed remedial actions, updated CA software, regenerated CRLs, and would correct a timing inaccuracy in the full report.
  3. Teliacompany representative — Telia filed the full incident report, including the timeline, impact statement, and remediation steps.
  4. Teliacompany representative — Telia said the CA ceremony documentation had been amended and that the corresponding action item was completed.
Participants
Teliacompany representative
External References
Similar Local Cases
#1896108 RESOLVED Self Reported Incident Certificate Misissuance Opened 2024-05-10 · Closed 2024-09-06 · 78% similar
Telia: Certificates Issued with lower case value in subject:countryName
#1920659 RESOLVED Certificate Misissuance Self Reported Incident Opened 2024-09-24 · Closed 2024-12-06 · 77% similar
Telia: S/MIME Certificate issued to expired domain
#1940957 RESOLVED Certificate Misissuance Self Reported Incident Opened 2025-01-10 · Closed 2025-06-20 · 77% similar
Telia: TLS OV certificate with subject countryName and localityName mismatch
#1859314 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-10-16 · Closed 2024-01-26 · 75% similar
Telia: TLS certificates issued in violation of TLS BR v2.0.1
#2081189 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-10-13 Still Open · 74% similar
ANF: Potential TLS BR 7.1.2.8 violations in OCSP responder certificate
#2076246 UNCONFIRMED Ca Certificate Compliance Self Reported Incident Incident Linting Quality Issue Opened 2026-09-28 Still Open · 74% similar
Apple: CRL is signed incorrectly
#2075878 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Repository Issue Opened 2026-09-26 Still Open · 73% similar
Disig: CRL contains not allowed attributes
#2011314 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Externally Reported Incident Opened 2026-01-19 · Closed 2026-06-23 · 72% similar
Netlock: unspecifed revocation code (0) in CRL

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

⚠

Confirm action