The short version
- The breach. DigiCert says an internal business system used to archive customer information was accidentally made reachable from the internet during a February 2025 server migration. An unauthorised account read archived records between 27 June and 2 July 2026.
- What was exposed. The records held names, business email addresses, phone numbers and business addresses. For some customers they also included identification documents such as a driver's licence, passport or utility bill.
- Late confirmation. DigiCert handled the June discovery as an account-creation problem. It began suspecting on 12 October that archived data had been read and confirmed the access on 19 October.
- Systems said to be unaffected. DigiCert says the account had read-only access and could not change records, approve certificate validations or issue certificates. Its certificate authority services, CertCentral and DigiCert ONE were not compromised, and customer login credentials were not taken.
- Numbers still unknown. DigiCert has not said how many customers are affected and says it is still reviewing identification documents to determine who was involved.
Timeline
| Date | Event |
|---|---|
| February 2025 | An internal system holding archived customer information is moved out of a VPN-restricted network and becomes reachable from the internet. |
| 21 June 2026 | DigiCert determines the system is externally accessible and that an unassigned account has been created. |
| 27 June - 2 July 2026 | An unauthorised account reads archived customer information. |
| 2 July 2026 | DigiCert blocks the unauthorised account and restricts access to the system. |
| 12 October 2026 | The company begins to suspect the account may have reached archived data and opens an investigation. |
| 19 October 2026 | DigiCert confirms archived customer information was accessed and treats the event as reportable. |
| 5-6 November 2026 | Customers share breach notification emails and the incident is reported publicly. |
How the exposure happened
According to a post-mortem DigiCert published on Mozilla's Bugzilla platform, a February 2025 server migration moved an internal business system used for archiving customer information off a network reachable only through a VPN. The move left it accessible from the internet. The system carried a self-registration feature built for other applications, which security news outlet SecurityWeek reports did not require multi-factor authentication, so outside users could create accounts. An authorisation flaw then gave those unassigned accounts read-only access to archived data.
DigiCert determined on 21 June 2026 that the system was externally reachable and that an unassigned account existed, and it blocked the account on 2 July. The access itself fell between 27 June and 2 July. The company says the account could not write records, act as a validation approver or issue certificates.
The company says the matter was first investigated and remediated as an account-creation event rather than a data-access event. It began to suspect archived data had been read on 12 October and confirmed the access on 19 October. Since then it has restricted access to the system, disabled self-registration, removed or verified remaining non-DigiCert accounts, reset passwords for all business system users, added access controls and monitoring, and checked permission policies on the system.
What was taken and who is affected
The archived data held names, business email addresses, phone numbers and business addresses shared with DigiCert. For some customers it also held personal identification documents provided during certificate validation, including driver's licences, passports and utility bills. DigiCert has begun sending breach notifications; cloud architect Fabian Bader published his on X, and other recipients posted similar emails, with several raising concern that identity papers could be tied to specific certificates.
DigiCert says its certificate authority services, the CertCentral portal and the DigiCert ONE platform were not compromised, that customer login credentials were not taken and that issued certificates remain secure. The company says it has found no evidence that the information has been misused, has reported the incident to law enforcement and declined to say whether the intruders had contacted it.
The notification says the company is still reviewing identification documents to establish who is affected and will write again when that review is complete. Neither DigiCert nor the news reports give a figure for the number of customers involved.
Why it went unnoticed
DigiCert attributes the delay to how the change was classified. The system migration was handled as an infrastructure change rather than a security change, which the company says would have triggered a more detailed review and sign-off. It also says the system gave too little warning of new accounts created through the externally reachable endpoint, or of request volume from its internal endpoints.
The company describes the access as a reportable event under rules set by Mozilla, Google Chrome, Microsoft and Apple for certificate authorities. It acknowledged the handling in its own report: "The incident was initially handled as an account-creation issue rather than a data-access event."
What is not known yet
- Who created the unauthorised account, and whether they are linked to any known group.
- How many customers' records were read during the five-day window.
- Which customers had identification documents involved; DigiCert says its review is incomplete.
- Whether any of the exposed information or documents has been used since, beyond DigiCert's statement that it has seen no evidence of misuse.
- What law enforcement has done since DigiCert reported the incident.
What to do
If you are a DigiCert customer
- Check for a breach notification from DigiCert and follow the instructions in it.
- If you submitted a driver's licence, passport or utility bill for certificate validation, treat that document as potentially exposed and watch for phishing that cites certificate or validation details.
- DigiCert says issued certificates and customer login credentials are unaffected, so there is no vendor instruction to replace certificates or reset your DigiCert account because of this incident.
- Wait for DigiCert's follow-up notification if your identification documents are still under review.
If you run internal business systems
- List any system moved off a VPN-only segment and check from outside whether it is reachable from the internet.
- Disable self-registration on internal applications and require multi-factor authentication for account creation.
- Alert on new accounts created through externally reachable endpoints and on unusual request volume from internal endpoints.
- Route network and infrastructure changes through security review and sign-off rather than treating them as routine operations.
For everyone else
- Ask vendors that hold copies of your identity documents how long they keep them, who can read them and how they are protected, because an internet-facing archive turns old verification files into a lasting risk.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.