DigiCert data breach: customer IDs exposed by a server move
The DigiCert data breach exposed archived customer contacts and some passports and licenses. Certificates are safe. Expect phishing that knows your cert history.
The company that vouches for your website's identity leaked some of its customers' identities. The DigiCert data breach exposed archived customer records, including names, business emails, phone numbers and addresses. For some customers, it also exposed the passports, driver's licenses and utility bills they sent in to get a certificate validated. The cause wasn't an advanced attack. A server move in February 2025 left an internal system open to the internet, and nobody noticed for over a year.
What actually happened
DigiCert explained the incident in a post-mortem on Mozilla's Bugzilla, as BleepingComputer and The Record report:
- The mistake. A February 2025 migration moved an internal business system out of its VPN-only network. The system had a self-registration feature, so outsiders could create accounts.
- The flaw. The new accounts weren't assigned to any application. An authorization bug still let them read archived customer data.
- The miss. DigiCert found unknown accounts in June 2026 and decided they couldn't reach data. It shipped a fix by July 2. Only on October 19 did it confirm that an outside account read customer records from June 27 to July 2. In DigiCert's own words, it treated the event "as an account-creation issue rather than a data-access event."
- What's safe. DigiCert says the account was read-only. It couldn't approve validations or issue certificates. CA services, CertCentral, DigiCert ONE, customer logins and issued certificates were not affected.
- What's unknown. DigiCert hasn't said how many customers were affected. It is still reviewing ID documents to find out whose were exposed.
DigiCert told The Record it has seen no misuse and has reported the incident to law enforcement.
Why the DigiCert breach matters for your business
Your certificates are fine. The risk is phishing that sounds real. An attacker who knows your name, your business address and that you buy certificates from DigiCert can write a very believable "your certificate is about to expire, re-verify now" email.
What we'd do this week:
- Did you get a DigiCert notice? If an ID document was included, treat it as exposed. Watch for identity fraud attempts against the person whose ID it was.
- Re-verify nothing from email. Log in to CertCentral by typing the URL. Never use a link in a message.
- Tell your team. Whoever handles renewals should know this phishing angle exists.
- Learn the real lesson. DigiCert's own report says the migration "was treated as an infrastructure change rather than a security change." Every time you move a server, ask: what can reach this now that couldn't before?
Key takeaways
- A 2025 server move left a DigiCert internal system open to the internet
- An outside account read archived customer data from June 27 to July 2, 2026
- Some records held passports, driver's licenses and utility bills
- Certificates, CertCentral and customer logins were not affected
- Expect targeted phishing; renew and re-verify only through a URL you type
Moving servers soon? We treat every migration as a security change: we map what's exposed before and after, and we set up alerts for new accounts and odd traffic. Talk to us before the move, or see how we build.
Sources: BleepingComputer, The Record.
- #digicert
- #data-breach
- #ssl-certificates
- #phishing
- #small-business-security
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
Zyxel GS1900 zero-day: the June patch didn't stop the hacks
Zyxel GS1900 hacks blamed on an old patched bug used a zero-day, CVE-2026-107441. The June fix didn't help. Install the 2.90 Patch 3 firmware on all 10 models.
Read itXen XSA-523: Claude-found bug lets one VM read any other VM
Xen XSA-523 lets a malicious guest read and write other VMs' memory, dom0 included. Anthropic's Claude found it. Patch and reboot hosts, or ask your VPS host.
Read it