DigiCert data breach: contact details and some ID documents
We publish these pages from public notices and reporting so you can understand what was exposed. Everything here is already public. Always confirm with the organization named in your notice.
DigiCert, the certificate authority that issues website and code-signing certificates, has confirmed that an outside account read part of the archived customer data in one of its internal business systems between June 27 and July 2, 2026. Most of the records were business contact details. A small share also held identity documents that customer representatives had submitted during certificate validation, such as driver's licenses and passports. DigiCert has not said how many people are affected.
What happened
DigiCert published its full incident report on Mozilla's Bugzilla tracker on November 1, 2026. It says an internal system "used to archive business contact and personal information provided by customers" was moved during a February 4, 2025 infrastructure migration and "inadvertently allowed this internal business system to be accessible externally." An account registration feature on that system let outside accounts be created without multi-factor authentication, and those accounts could read archived data. (Confirmed)
According to the report, DigiCert learned of the outside access on June 21, 2026, and released a fix on July 2. It did not realize at that point that data had been read. On October 19, 2026, it "confirmed unauthorized access to a subset of archived data and determined this to be a reportable event." (Confirmed)
DigiCert says the incident "affected only a small proportion of archived data," and that its certificate authority services, CertCentral and DigiCert ONE were not affected. It also says customer login credentials and issued certificates "remain secure, valid, and fully trusted." (Confirmed) BleepingComputer and The Record reported on November 5 and 6 that DigiCert has started notifying affected customers and has not given a count. (Reported)
Sources
- DigiCert: Unauthorized access to business system (Bug 2084460), DigiCert, official incident report, October 21 and November 1, 2026
- DigiCert data breach exposes customer information, identity documents, BleepingComputer, November 5, 2026
- DigiCert certificate authority reports data breach, The Record, November 6, 2026
What data was involved
The incident report describes two groups of records:
- Business contact details (most records). In DigiCert's words: "Most of the data was limited to business contact information for customers: names, business email addresses, phone numbers, and business addresses." (Confirmed)
- Identity and address documents (a small minority). "A small minority of customer accounts included additional personal data in the form of a customer-provided document such as a driver's license, passport, utility bill, or other document with name and address." (Confirmed)
The access was read-only. DigiCert says it "could not write records, act as a validation approver, or issue certificates." A DigiCert spokesperson told The Record there is no evidence so far that the information has been misused. (Reported)
The people affected are mostly employees or representatives of DigiCert's business customers, not website visitors. If you submitted your own driver's license, passport or a utility bill to DigiCert to verify your identity for a certificate order, your personal documents may be in this set. Those documents typically show your home address, date of birth and ID number, which are the same details that people-search sites and identity thieves look for.
What affected people can do now
- Read the DigiCert notice carefully, if you received one. It should say whether an ID document of yours was involved. If you are unsure, contact DigiCert through the support channel listed in your account, not through links in an unexpected email.
- Expect targeted phishing. Names, work emails and phone numbers are enough for convincing messages that claim to be from DigiCert or a certificate vendor. Do not approve validation requests, reset passwords or share documents in response to a message you did not expect.
- If your driver's license was involved, check with your state motor vehicle agency on whether it can flag or replace the license number. Watch for accounts or loans opened in your name.
- If your passport was involved, consider reporting it to the issuing authority and asking about replacement. In the US, the State Department handles lost or stolen passport reports.
- Consider a credit freeze with Equifax, Experian and TransUnion if an identity document with your home address and date of birth was exposed. A freeze is free and blocks most new credit applications in your name.
- Check what is already public. A home address from an ID document is often already listed on people-search sites. Removing those listings reduces how easily someone can link your name, address and phone number.
What to do after a breach
- A company emailed me about a breach: what should I do?
- Dark web data versus data brokers
- What to do after a data breach
A free Delist scan checks open-web exposure we support: people-search sites, public records, data brokers, and breach-source signals. Signals are not live listings, and this is not removing you from a dump, a DMV database, or a vendor's private ID store.
More breaches
Free personal data exposure scan
We search the open web for your personal data and show what’s exposed. The scan is free. Removal and monitoring require a paid plan.