If your organisation buys SSL/TLS certificates from DigiCert or has submitted identity documents for domain validation, check whether DigiCert has contacted you. The certificate authority has warned that a misconfigured server migration exposed a slice of archived customer data — and for some people that included driver's licences, passports and utility bills.
What happened
BleepingComputer reported that DigiCert warned of a data breach after a server migration mistakenly exposed an internal business system to the internet. DigiCert says the breach affected a small portion of archived customer data: names, business email addresses, phone numbers and business addresses. For some people, the exposed records also held personal identification documents such as driver's licences, passports and utility bills.
An incident report on Mozilla's Bugzilla platform explains that a February 2025 server migration put a previously VPN-only internal system on the public internet. That system offered self-registration intended for other applications. An authorisation flaw then let externally created accounts read archived customer information in read-only mode.
DigiCert first found unauthorised accounts in June 2026 but initially believed they could not reach customer information. After a report through its managed security research program, it restricted access and fixed the authorisation flaw — still without realising archived data had been accessed. Further investigation, confirmed on 19 October 2026, showed an unauthorised account had accessed customer information between 27 June and 2 July 2026. DigiCert has acknowledged the incident was initially handled as an account-creation issue rather than a data-access event.
DigiCert says the unauthorised account had read-only access and could not modify records, approve validations or issue certificates. It also says certificate authority services, CertCentral and DigiCert ONE were not compromised, and that customer login credentials and issued certificates remain secure. DigiCert has restricted access, disabled self-registration and added further access controls. DigiCert is sending breach notifications and is still reviewing identification documents to determine who was affected. BleepingComputer asked how many people were impacted; no headcount has been published yet.
Who is affected
Anyone whose archived DigiCert customer record held contact details — and especially anyone who uploaded a driver's licence, passport, utility bill or similar document for validation — may be in scope. DigiCert has said the exposure covered a small portion of archived data, not the full customer base, and that it is still reviewing ID documents to identify those affected.
Australian small and medium businesses that buy DigiCert certificates, or that asked staff or directors to submit personal ID for organisation or domain validation, should watch for DigiCert's notification. DigiCert's statement is that certificates themselves and CertCentral / DigiCert ONE logins were not compromised — this is a privacy and identity-misuse problem, not a mass certificate-revocation event.
Why it matters for Australian businesses
Supplier breaches are a routine way attackers get names, emails, phone numbers and copies of ID. Once those details leave a vendor's archive, they can fuel targeted phishing, social-engineering calls that quote real company details, and longer-term identity misuse against directors or staff who submitted documents.
Even when certificates remain valid, exposed PII raises the risk that someone impersonates DigiCert, your registrar or your own IT team. Staff who recently validated a domain or renewed a certificate are particularly likely to trust a follow-up email that asks them to "confirm" details.
The Australian Cyber Security Centre's Essential Eight still applies: strong patching, multifactor authentication and restricting administrative privileges reduce how far a phishing click can go. For identity document exposure, the Office of the Australian Information Commissioner's guidance on identity fraud and Scamwatch are practical places to start if you or a staff member may be affected.
What to do now
- Watch for DigiCert's notification. DigiCert is still determining who had ID documents in the exposed archive. If you used DigiCert for certificates or validation, check spam and ask your certificate admins whether a notice arrived.
- Assume phishing will follow. Brief finance, IT and anyone who handles certificates that emails or calls claiming to be DigiCert, or asking for more ID, need a known-good channel check before anyone replies or clicks.
- Do not revoke certificates on rumour alone. DigiCert says issued certificates and CertCentral / DigiCert ONE credentials remain secure. Follow DigiCert's official advice if they later ask for specific certificate actions.
- If ID documents may have been exposed, follow OAIC and Scamwatch steps. Monitor banking, consider a credit-report check or ban, and use the OAIC identity-fraud guidance and Scamwatch reporting if something looks wrong.
- Review what ID you send to suppliers. Prefer the minimum document any certificate authority actually needs, and keep a register of which vendors hold director or staff ID.
- Tighten the rest of the identity chain. Phishing-resistant MFA and clear verification rules for invoice or bank-detail changes still cut the damage if a supplier leak becomes a spear-phish against your team.
How MSP Logic can help
If DigiCert (or another supplier) notifies you that contact details or identity documents were exposed, we can help you brief staff, tighten phishing and identity controls, and review how certificates and domain validation are handled in your environment. That work sits under our cybersecurity services.
Want a practical check of supplier risk and what to tell your team after a vendor breach notice? Get in touch and we'll take a look.
Source: BleepingComputer – DigiCert data breach exposes customer information, identity documents. This article is MSP Logic's own summary and advice; read the original report for full details.