What a DigiCert Account Read in Archived ID Records Between June 27 and July 2, 2026
DigiCert says an unauthorized account read archived validation records from June 27 to July 2, 2026. Certificate issuance was not affected, its report says.

BleepingComputer reported on Nov. 5, 2026 that an unauthorized account read archived customer records held in one of its internal business systems. According to the company's incident report, filed with Mozilla's root program, the access window ran from June 27 to July 2, 2026. The archive holds information customers provided so DigiCert could validate the identity of their representatives.
As of Nov. 8, 2026, DigiCert had not published how many customers were affected. Notifications have started, and the company is still reviewing identity documents to determine who was affected, BleepingComputer reported on Nov. 5.
What the Archive Held and Who Was Affected
DigiCert's report says most exposed records contained business contact information: names, business email addresses, phone numbers and business addresses. For a small minority of customer accounts, the archive also held driver's licenses, passports or utility bills. DigiCert describes the affected portion as a small proportion of its archived data.
Neither the incident report nor the news coverage gives a count of affected people, records or organizations. Commenters on Mozilla's bug thread have asked for the number of affected records and whether the exposed data was used in subscriber validation. In a later comment on the thread, a commenter said DigiCert's response did not answer those questions. BleepingComputer said it had asked how many people were affected and had not received a response.
How a 2025 Migration Opened the Archive
The root cause dates to a Feb. 4, 2025 migration. That move took an internal system out of a VPN-restricted network segment, and the system then had a self-registration feature, Cyber Security News reported on Nov. 5. Accounts created through that feature could read archived records because of a gap in permission checks. Cyber Security News also reported that these accounts were not covered by the multifactor authentication required for DigiCert staff.
The incident report's timeline says DigiCert staff observed non-DigiCert accounts on June 18, 2026, and an early review concluded they had no data access. DigiCert determined on June 21, 2026, after a report from a managed security research program, that the system was externally accessible.
Both accounts agree that an authorization fix shipped on July 2, and that DigiCert first suspected archive access on Oct. 12 and confirmed it on Oct. 19. BleepingComputer quotes the company as saying the event was initially handled as an "account-creation issue." A preliminary incident report was filed on Oct. 20.
What DigiCert Says Was Not Affected
DigiCert states that the unauthorized account had read-only access and could not write records, approve validations or issue certificates. Its incident report says no certificates were issued, modified or revoked, and that certificate issuance was not stopped. The log review found no validation actions linked to the account.
The company says its certificate authority services, CertCentral and DigiCert ONE were not affected, and that customer login credentials and issued certificates were not compromised. The certificate authority systems are described as sitting on separate network segments and not accessed. Cyber Security News reports that customers do not need to replace active certificates.
The breach reached the identity-check files behind certificate orders, while DigiCert says no certificate was issued, changed or revoked. For companies that buy DigiCert certificates, the report separates the certificates from the archive, and describes the certificates and the systems that issue them as unaffected.
Remediation, Reporting Rules and Open Questions
DigiCert's incident report lists several steps. It blocked new registrations at a web application firewall on June 18, restricted hostnames to VPN traffic on July 9 and reset business system passwords on Oct. 17. Self-registration was deactivated on Oct. 24, and file access and request-volume alerts were added on Oct. 15.
The report also says the company has contacted affected customers and reported the incident to law enforcement. The bug filing says all action items are complete, including an internal audit. A table in the same filing lists the audit and a final alerting review as ongoing, with a Nov. 6 due date, while a later comment says the action items are complete.
Mozilla's incident-response guidance asks certificate authorities for an initial report within 72 hours of learning of an incident, and for progress updates at least every week. The preliminary report was filed on Oct. 20, one day after DigiCert confirmed the access.
Open questions include the number of affected records and whether the exposed data was used in subscriber validation. DigiCert has offered summary statistics to Mozilla's root program representatives on request, according to the bug filing. Notifications are going out while the document review continues, and no completion date for that review has been given.






