← Apple Inc. cases
Bugzilla #2076246 Ca Certificate Compliance Self Reported Incident Incident Linting Quality Issue

Apple: CRL signed with the wrong ECDSA hash algorithm

UNCONFIRMED Apple Inc.
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

Apple reported that one of its CRLs was signed with ecdsa-with-SHA384 when, because the signing key is P-256, it should have been signed with ecdsa-with-SHA256 under Baseline Requirements section 7.1.3.2.2. Apple said the affected CRL was for Apple Public EV Server ECC CA 1 - G1 and that the issue did not affect any certificates. In its full incident report, Apple said it corrected the CRL and issued a new one, and that issuance of leaf certificates was not stopped because the problem did not impact them. Apple also stated that there was no revocation delay. The report says the issue was discovered after DigiCert received a Certificate Problem Report from a community member and notified Apple. Apple later said all action items were completed and that, if there were no further questions, its next update would be a closure report.

Model: gpt-5.4-mini Generated: 2026-10-20 17:32 UTC Confidence: 0.97 4 comments
Chronology
  1. Baseline Requirements version 1.7.1 became effective, requiring ecdsa-with-SHA256 on P-256 curves.
  2. A Certificate Problem Report was received about the CRL signature algorithm issue.
  3. Apple corrected the CRL and issued a new one.
Thread Activity
  1. Apple representative — Apple filed a preliminary incident report describing the CRL signature mismatch and said DigiCert had been notified through a certificate problem report.
  2. Apple representative — Apple said it was still monitoring the incident and would post the full report by October 9, 2026.
  3. Apple representative — Apple posted the full incident report, including the timeline, impact, root cause analysis, and related incidents.
  4. Apple representative — Apple said all action items were completed and that its next update would be a closure report if there were no further questions.
Participants
Apple representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#1841534 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-07-03 · Closed 2023-08-30 · 81% similar
Apple: TLS certificates issued outside the TTL of the CAA record
#1955365 RESOLVED Self Reported Incident Opened 2025-03-20 · Closed 2026-07-28 · 81% similar
Apple: Public Key Reuse
#1730291 RESOLVED Incident Opened 2021-09-11 · Closed 2024-06-30 · 80% similar
Apple: Test website certificates expired
#1659316 RESOLVED Incident Opened 2020-08-16 · Closed 2023-02-22 · 79% similar
Apple: EV Certificate Approver Authorization
#1588001 RESOLVED Self Reported Incident Opened 2019-10-11 · Closed 2023-02-22 · 78% similar
Apple: OCSP responders return responses with incorrect issuer
#1669618 RESOLVED Incident Opened 2020-10-07 · Closed 2023-02-22 · 78% similar
Apple: Empty SingleExtension in OCSP responses
#1724528 RESOLVED Incident Opened 2021-08-06 · Closed 2024-06-30 · 78% similar
Apple: Intermediate CA certificates omitted from audit statement
#1771398 RESOLVED Incident Opened 2022-05-26 · Closed 2023-02-22 · 78% similar
Apple: OCSP responders return ‘unknown’ for valid S/MIME and TLS certificates

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

⚠

Confirm action