DigiCert certificate private key compromised, then reused for a new certificate

Status
Open
Disclosed

TL;DR: DigiCert, a provider of digital trust and security solutions, says it issued a certificate on a private key that a community member had already demonstrated as compromised. DigiCert has since revoked the new certificate and added the key to its compromised key blocklist.

What happened

DigiCert issued a certificate whose private key matched a certificate it had earlier revoked with reason keyCompromise. A community member had first reported the private key as compromised by email, demonstrating compromise with a message signed with the private key. That report did not use the Problem Report web tool that the DigiCert CP/CPS directs, and DigiCert Support did not direct the reporter to the tool.

DigiCert Support verified the signature, revoked the first certificate with reason keyCompromise within 24 hours, and notified the subscriber. DigiCert did not add the public key to its compromised key blocklist, a step performed automatically only for reports submitted through the Problem Report tool. The community member then requested and was issued a new certificate using the same key pair, and filed a Certificate Problem Report.

DigiCert revoked the new certificate and added the private key to its compromised key blocklist.

Timeline

  1. Reported in Mozilla Bugzilla bug 2092247

Sources

  1. Mozilla Bugzilla, bug 2092247bugzilla.mozilla.org, Nov 12, 2026