← DigiCert cases
Bugzilla #1339339 Ca Certificate Compliance Certificate Misissuance

DigiCert: Non-BR Compliant Certificates - missing CP/CPS OID

RESOLVED FIXED DigiCert
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

The case reports that certificates issued by new CAs in a DigiCert-related SSL issuance environment were missing the CP/CPS OID during preproduction testing. The issue was identified as non-aligned with the Baseline Requirements, even though the CA stated it did not represent a security issue and only a handful of impacted certificates were public-facing. DigiCert located the error causing the mislabeling and corrected it, and stated that certificates were otherwise issued in accordance with Baseline Requirements. DigiCert also reported revocation progress: 80% of the certificates were revoked initially, with the intent to revoke 100% by the next update. The thread later states that all of these certs were revoked, and that the system was patched to ensure a CP OID is included each time. The bug is marked RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 11:02 UTC Revised: 2026-06-16 18:38 UTC Confidence: 0.86 5 comments
Chronology
  1. During preproduction testing of a new SSL issuance environment, DigiCert identified that certificates issued by new CAs were missing the CP/CPS OID.
  2. DigiCert corrected the error causing the CP/CPS OID mislabeling and began revoking impacted certificates.
  3. DigiCert reported that all impacted certificates were revoked.
  4. DigiCert stated the system was patched to include the CP OID each time and indicated the issue could be closed.
Thread Activity
  1. DigiCert — Jeremy Rowley explained that certificates issued in a new environment were missing the CP/CPS OID, identified the error, corrected it, and stated Microsoft took action to prevent recurrence.
  2. Mozilla representative — Kathleen Wilson asked to be kept updated on remaining action items and when the concern was fully resolved.
  3. DigiCert — Jeremy Rowley reported that 80% of the certificates had been revoked and that 100% would be revoked by the next update.
  4. DigiCert — Jeremy Rowley updated that all of these certs are revoked.
  5. DigiCert — Jeremy Rowley suggested the bug could be closed, stating all certs were revoked and the system was patched to include the CP OID each time.
Participants
DigiCert Mozilla representative
External References
Similar Local Cases
#1727963 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2021-08-28 · Closed 2023-02-22 · 99% similar
DigiCert: Truncation of Registration Number
#1827772 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2023-04-13 · Closed 2023-05-04 · 98% similar
DigiCert: Org-JOI type mismatch
#1447192 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2018-03-20 · Closed 2023-02-22 · 98% similar
DigiCert: Onion Certs
#1438216 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2018-02-14 · Closed 2022-11-14 · 97% similar
DigiCert: Incorrectly issued EV Certificate
#1353827 RESOLVED Certificate Misissuance Opened 2017-04-05 · Closed 2023-02-22 · 96% similar
DigiCert: DigiCert issued cert with CN too long
#1397968 RESOLVED Certificate Misissuance Opened 2017-09-08 · Closed 2023-02-22 · 95% similar
DigiCert / Verizon: Reserved/Intranet domain name
#1465600 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2018-05-30 · Closed 2023-02-22 · 92% similar
DigiCert: Invalid Country Code Issuance
#1436173 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2018-02-06 · Closed 2023-02-22 · 91% similar
DigiCert: SCEE / Justica: Non-BR-Compliant Certificate Issuance

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

Confirm action