Good to knowPlatform changes

DigiCert says an archive system left open by a 2025 migration was read for six days in 2026: your certificates are fine, but watch for phishing and check the notice

DigiCert's own incident report says a system that archives what customers send it became reachable from the internet in February 2025, and that an unauthorized account read business contact details, and for a small minority an ID document, between 27 June and 2 July 2026. It says no certificate was affected. What it says, what it does not, and what to check.

How urgent

Good to know

Who is affected

Business customers of DigiCert whose contact details, or an identity document used to prove who they are, sit in its archive. DigiCert does not say how many. Websites that only use DigiCert certificates are not shown to be affected

What to do

You do not need to reissue certificates (DigiCert says no action is needed on active certificates). Read any DigiCert notice you received, treat a document it names as exposed, and expect phishing that imitates DigiCert. Type the address of your account yourself instead of using email links

Published 8 Nov 2026 · Sources last checked 8 Nov 2026No. 63 / 87

What happened

DigiCert is a certificate authority: one of the companies that issue the certificates behind the padlock in your browser. In an incident report to the Mozilla CA program, it says an internal business system that archives information its customers provide was exposed. In February 2025 an infrastructure migration moved the system from a network segment restricted to the company VPNVPN A private encrypted tunnel between your device and a network, so traffic does not travel in the open. Tap again to open the glossary into another availability zone, and it became reachable from the internet.

The system runs its own copy of the account platform DigiCert uses for customer products. That platform lets people register an account themselves, a feature the business system was never meant to use. Accounts created that way needed no multi-factor login and were read-only by default, but they could read the archived data.

The timeline in DigiCert's report:

  • 18 June 2026: the internal team saw accounts that were not DigiCert's and concluded they had no data access. It put the system behind a web firewallFirewall A filter that decides which network traffic may reach a device or service and which is blocked. Tap again to open the glossary that blocked new external accounts.
  • 21 June: a report came in from its managed security research program about the external account creation.
  • 27 June to 2 July: the window in which, according to DigiCert, an unauthorized account read data. An authorization fix went to production on 2 July.
  • 12 October: DigiCert first suspected unauthorized access to the archive and began investigating. The report says the incident "was initially handled as an account-creation issue rather than a data-access event."
  • 19 October: it declared a reportable event and confirmed the access window with file access and request logs. The preliminary report was filed on 20 October.

What was read, in DigiCert's words: "most of the data was limited to business contact information": names, business email addresses, phone numbers and business addresses. "A small minority" of customer accounts also held a customer-provided document, such as a driver's license, passport or utility bill. The access was read-only: it could not write records, approve validations or issue certificates. DigiCert says no certificate was affected, and that its certificate authority services, CertCentral and DigiCert ONE "were unaffected." Customer login credentials and DigiCert-issued certificates "remain secure, valid, and fully trusted."

On customers it says only: "No action is needed from customers regarding active certificates." It says it has contacted the affected customers and reported the incident to law enforcement. A customer notice quoted by The Register says DigiCert is "completing a review of identification documents to determine the specific individuals involved."

The Register's headline says 16 months. That is roughly how long the system was reachable (February 2025 to the June 2026 firewall change). The data was read for six days. DigiCert's report does not give a single end date for the exposure.

Who is affected

  • Business customers whose details are in the archive. That includes people who gave DigiCert an identity document to prove who they are. DigiCert has not said how many customers.
  • Not shown to be affected: your website certificates and your HTTPSHTTPS The secure version of the web address protocol: it encrypts what travels between a visitor and your site and checks that the site is the real one. Tap again to open the glossary. DigiCert says none was issued, changed or revoked through this access.
  • Anyone who gets a DigiCert email. Contact details like these are what phishingPhishing A message or page that pretends to be someone you trust to get you to hand over a password, a code or a payment. Tap again to open the glossary is built from.

What to do

  1. Do not reissue certificates because of this. DigiCert says no action is needed on active certificates, and we found nothing contradicting it.
  2. Read the notice if you got one. DigiCert says affected customers were contacted with information specific to them. If it names an identity document, treat that document as exposed and watch for identity fraud.
  3. Expect phishing that imitates DigiCert, for example a renewal or an "identity verification" request. Do not follow email links: type the address of your account yourself. The names and company details leaked here make a convincing message easy to write. This advice is ours, not DigiCert's.
  4. If you do not remember what you sent DigiCert, check your account or ask support what is on file for your organization.
  5. A lesson for your own systems (ours, not DigiCert's): after you move a system to a new network or provider, check from the outside that it is still private. And turn off self-registration on any internal tool that does not need it.

What we could not confirm

DigiCert does not say how many customers or identity documents are involved, and its report does not say whether the archive feeds its customer validation: a Mozilla participant asked and, in the thread we read, got no answer. We did not find a customer notice on DigiCert's own site, only the text quoted by the press, and we could not open The Hacker News. DigiCert says "may have included" and "in some cases" for the documents, and it is still reviewing which people are involved, so whether your document was seen is not settled. Some press pieces say "hackers" or "were compromised"; DigiCert's report says only "unauthorized account." Nobody has named an actor. We have not tested anything on DigiCert's systems.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks