DigiCert confirms identity-document leak through an internal system exposed by a network migration
On 5 November 2026, certificate authority DigiCert published an incident report about an internal business system accidentally exposed to the internet since February 2025, whose self-registered accounts could read archived identity documents. No certificate was issued or compromised, but the incident shows a network boundary is not an access control.
4 February 2025. An infrastructure migration moves a DigiCert business system off a VPN-restricted network segment into another availability zone — and accidentally exposes it to the internet with no security review. 19 October 2026. The certificate authority confirms unauthorized access to archived data. 5 November 2026. The incident report goes public, and Troy Hunt shares the customer notification. Why it matters: no certificate issuance or revocation is at stake, but a certificate authority has just shown that its network boundary did not do the access-control job everyone assumed it was doing.
Access born of a migration, not a sophisticated intrusion
The starting point is mundane in a way that should alarm any CISO. On 4 February 2025, DigiCert moved a business system — the one holding customer contact details and identity documents — from a VPN-protected segment to another availability zone. The move exposed the system to the internet without a security review of that new exposure.
In the same window, an account self-registration feature, built for other uses of the account-management platform, became reachable. Accounts created through it were not covered by the multi-factor authentication required of DigiCert staff. Even with no application assigned, they received read-only access to archived information — a gap in the permission checks.
The detection timeline is just as instructive. On 18 June 2026, staff noticed non-DigiCert accounts. A first review wrongly concluded that accounts with no assigned application could not read data. A WAF blocked new registrations through the external path, but existing access stayed open. On 21 June, a report from the managed security research program followed, and the authorization fix only shipped on 2 July.
An exposure window rebuilt from logs
Investigators established that unauthorized access occurred between 27 June and 2 July 2026. It was only on 12 October that DigiCert first suspected access to the archives, relying on retained logs and audit records. On 19 October the access was confirmed, and the preliminary incident report was filed the next day.
What leaked is precise, and that precision is what matters. The exposed data includes names, business email addresses, phone numbers, and business addresses. A small minority of customer accounts also held passports, driver’s licenses, utility bills, or other identity documents. The report gives no total count of affected people or documents, and DigiCert says it is still reviewing records to notify individuals one by one.
The nuance everyone should take away
The most important part of the report is what was not compromised. The certificate authority services, CertCentral, and DigiCert ONE, stayed out of reach. Investigators found no certificate issuance, validation, or revocation tied to the unauthorized account, and customer login credentials and already-issued certificates remain intact. DigiCert is categorical: customers do not need to replace their active certificates.
That separates this incident from two earlier ones under the same roof. The 2023 support-system compromise around code-signing certificates, and the 2024 DNS validation error that forced the revocation of thousands of certificates, both struck the core business. Here, the account could only read — it could not modify, could not approve an identity check, could not issue.
The incident report filed on Mozilla’s Bugzilla — the browser community keeps a close eye on its CAs — lists the corrective actions: disabling self-registration, moving exposed endpoints back behind private infrastructure, resetting passwords, reviewing permissions, and requiring security approval for any network-exposure change.
The verdict
If you are a DigiCert customer, you have nothing to do about your certificates — no replacement is required — but treat the identity documents involved as exposed and stay alert for individual notifications. If you operate an internal system, take the structural lesson: a migration that moves a service off the VPN is a security-posture change in its own right, requiring an exposure and permission review, not just an infra ticket. If you run a platform with self-registration, check that such accounts inherit no rights by default. The real lesson of the DigiCert incident fits in one sentence: a network boundary had been doing, in people’s heads, the job of an access control that did not exist.