The DigiCert data breach exposed an internal system of the certificate authority DigiCert to the internet, following an error made during a server migration in February 2025. Names, business emails, phone numbers and addresses could be read, and, for a minority of accounts, identity documents. The story was revealed on November 5, 2026 by Lawrence Abrams, in a BleepingComputer article based on the notice sent to customers.
DigiCert says its certificate authority services, CertCentral and DigiCert ONE were not compromised. No figure on the number of affected customers has been published so far.

What happened in the DigiCert data breach?
A migration carried out on February 4, 2025 moved an internal archive system from a VPN-only segment to a zone reachable from the internet, according to DigiCert’s incident report on Bugzilla. A self-registration feature, meant for other applications, then let anyone create an account.
Those accounts were assigned to no application and did not require multifactor authentication, but an authorization flaw gave them read access to the archives, according to The Register. On June 18, 2026, an internal team noticed outside accounts and wrongly concluded they could reach no data. An unauthorized account nonetheless read data between June 27 and July 2, 2026, the day an authorization fix was deployed.
DigiCert only suspected data access on October 12, then confirmed it on October 19. The company acknowledges that the incident was first handled as an account-creation problem rather than a data-access event. Customer notifications began in early November, as BleepingComputer reported.
What data did the DigiCert data breach expose?
For most records, it is names, business email addresses, phone numbers and business addresses. For a minority of accounts, DigiCert says customer-provided documents, such as a driver’s license, a passport or a utility bill, may have been viewed.
DigiCert speaks of a “small proportion” of its archived data, without giving a figure. It states that customer login credentials and issued certificates are not affected. DigiCert is still reviewing identity documents to identify the people involved and notify them afterwards.
How long was the system exposed?
It depends on what you measure. The system stayed reachable for about 16 months before DigiCert spotted the accounts, but the only reconstructed data reading lasts six days, from June 27 to July 2, 2026. Sources differ:
- Exposure length: The Register and eSecurity Planet speak of more than 16 months, while IT-Connect says nearly 17 months. The gap probably comes from the end point chosen, since the report dates the shutdown of self-registration to October 24, 2026, more than twenty months after the migration by our calculation.
- Detection delay: IT-Connect mentions about three months, while the report’s dates give nearly four months between June 18 and October 19.
- End of the incident: The Register writes that DigiCert closed the account-creation problem on July 2, BleepingComputer gives no date for disabling self-registration, and the report sets it at October 24, the July 2 fix having only closed access to the archives.
Are certificates affected by the DigiCert data breach?
No, according to DigiCert: the unauthorized account was read-only, could neither approve validations nor issue certificates, and logs show no validation, issuance or revocation activity tied to it, per the report as summarized by Rescana. These claims come from DigiCert itself.
The Register notes that DigiCert did not answer its questions before publication, and we found no independent analysis. Rescana points out that the report does not treat organization-validated or EV certificates separately, and advises against a blanket reissue: it is better to follow the notice you received.
Our analysis: what the DigiCert data breach changes
This section is our analysis. Based on the published facts, the risk to customers is mostly human: a name, a job role, contact details and DigiCert customer status are enough to write a credible fake renewal email, as IT-Connect points out. Our guide to phishing explains this mechanism.
The identity documents raise another issue. The report describes a system that archives customer-provided information for validation, and DigiCert does not explain why those documents were still kept or for how long. Rescana does recommend asking for that justification. Finally, the report states that authorization must not depend on a system’s network position: a simple segment change was enough.
What measures has DigiCert taken?
DigiCert says it closed access to the archives, disabled self-registration and strengthened monitoring. According to its Bugzilla report, these measures were spread from June to October 2026:
- June 18, 2026: a web application firewall blocks external account creation.
- July 2 and 9, 2026: an authorization fix returns a 401 error to accounts with no assigned application, then the system’s hostnames are limited to VPN traffic, except approved endpoints.
- October 15 and 17, 2026: alerts on file access and request volume are added, and passwords of the system’s internal users are reset.
- October 24, 2026: self-registration is disabled and the remaining endpoints move behind private addresses.
- October 29 and 30, 2026: a security owner for the system is named and the least-privilege review is completed.
DigiCert also says it contacted affected customers and informed law enforcement, without dates or numbers.
What to do after the DigiCert data breach if you are a customer
Contact DigiCert through a channel you already know to find out whether your records and documents are involved, and treat any unexpected request as suspicious. There is no need to reissue your certificates by reflex, according to DigiCert and Rescana.
Do not circulate copies of identity documents in ordinary tickets. If an employee’s document is involved, inform the person and your legal team or DPO. According to eSecurity Planet, also ask the issuing authority, knowing that a replacement does not retrieve copies already exposed.
Frequently asked questions about the DigiCert data breach
An internal DigiCert archive system, made reachable from the internet by a migration in February 2025, was read by an unauthorized account from June 27 to July 2, 2026. DigiCert confirmed the access on October 19, 2026.
Names, business emails, phone numbers and business addresses, and for a minority of accounts identity documents such as a license, a passport or a utility bill.
That number has not been published. DigiCert speaks of a small proportion of the archived data and is still reviewing identity documents.
DigiCert says no certificate was affected, issued, modified or revoked because of the incident, and Rescana advises against a blanket reissue. Follow the notice you received.

