CVE Tools
A server rack bathed in cold blue light, one cable visibly rerouted from an internal switch to an external uplink port, seen from a low angle in a dim data center aisle

DigiCert Closed the Hole on July 2. It Took Until October 12 to Check Whether Anyone Had Walked Through.

A February 2025 server migration quietly moved a customer-ID archive onto the open internet. DigiCert spotted the stray accounts in June, blocked them, and then didn't check what they'd actually touched for another three and a half months.

On November 1, 2026, certificate authority DigiCert filed a full incident report on Mozilla's public CA-compliance Bugzilla tracker (bug 2084460). It describes a 16-month chain of events that started with a routine infrastructure migration and ended with a third party reading archived customer ID documents — passports, driver's licenses, utility bills — for five days in the summer of 2026.

What actually happened, in order

16 months, from migration to full report

  1. Internal archive system migrated off its VPN-restricted segment
    A business system used to archive customer-submitted ID documents was moved to an internet-reachable availability zone. Per DigiCert's filing, the change was tracked as infrastructure work, not a security change — so it bypassed the review that would normally flag new external exposure.
  2. DigiCert spots unfamiliar accounts, calls them harmless
    Internal staff noticed accounts that weren't assigned to any application and judged the anomaly low-risk. DigiCert deployed a WAF rule blocking new account creation the same day.
  3. DigiCert's own security research program raises the same flag
    A researcher inside DigiCert's security program flagged the possibility that the accounts had been created externally — three days after the first sighting.
  4. Unauthorized read access to the archive begins
    DigiCert's investigation later determined the actual data-access window started here, using one of the unassigned accounts.
  5. The hole is patched — but not investigated
    DigiCert deployed an authorization fix (unassigned accounts now get a 401) and the access window closed. At this point DigiCert still treated it as an account-creation event, not a data-access event.
  6. Policy fix and pen test, while the data question sits unasked
    DigiCert adopted a mandatory security sign-off policy for future network changes and ran a third-party penetration test — process fixes, still with no active inquiry into what the June accounts had actually read.
  7. DigiCert first suspects the accounts read archived data
    More than three months after closing the vulnerability, DigiCert began investigating whether the blocked accounts had accessed customer records — not whether more could get in.
  8. Formal determination: this is a reportable event
    DigiCert classified the incident under the disclosure rules that Mozilla, Google Chrome, Microsoft and Apple impose on certificate authorities.
  9. Full incident report filed on Mozilla's Bugzilla
    Bug 2084460 lays out the timeline, root cause, and a 13-item remediation checklist, two items still marked ongoing with a due date of November 6.
  10. Remediation checklist closed out; press coverage follows
    DigiCert told Recorded Future News it has no evidence the archived information has been misused and has referred the matter to law enforcement. The Register and others publish critical coverage of the 16-month timeline the same day.
16 moFrom migration to full incident reportFeb 4, 2025 → Nov 1, 2026
5 daysActual unauthorized read-access windowJune 27 – July 2, 2026
~3.5 moGap between closing the hole and checking what it costJuly 2 → October 12, 2026
13Remediation action items DigiCert committed to11 complete by Nov 1; all 13 by Nov 6 per the Bugzilla thread

What was actually exposed — and what wasn't

DigiCert has not published a count of affected customers or records; its filing and its customer notifications both describe the identity-document exposure as a "small proportion" of the archive. The split between the certificate authority's core trust function and the business system that leaked matters more than the headline:

The archive vs. the certificate authority

What was exposed
  • Names, business email addresses, phone numbers, business addresses for a subset of customers
  • For a smaller subset: identity documents — driver's licenses, passports, utility bills submitted for identity verification
  • Read-only access only — the account could not write records
Confirmed via DigiCert's own Bugzilla filing.
What was not touched
  • CertCentral and DigiCert ONE platforms
  • Certificate issuance, revocation, and validation workflows — zero certificates affected
  • Customer login credentials to DigiCert's core services
DigiCert states the compromised account could not act as a validation approver or issue certificates.

The remediation checklist

ActionStatusDate
WAF rule blocking the registration endpointComplete2026-06-18
Authorization fix: 401 for unassigned accountsComplete2026-07-02
VPN-only restriction enforced at the WAFComplete2026-07-09
Mandatory security sign-off for network changesComplete2026-08-28
Third-party penetration testComplete2026-08-31
New file-access / request-volume alertingComplete2026-10-15
Password reset for all business-system usersComplete2026-10-17
Self-registration feature fully deactivatedComplete2026-10-24
Migration to private-IP load balancersComplete2026-10-24
Per-endpoint authorization / least-privilege reviewComplete2026-10-30
Audit: confirm no origin server is externally reachableMarked ongoing in the filingDue 2026-11-06
Final review of account-creation alerting, with SOC escalation pathMarked ongoing in the filingDue 2026-11-06

Thirteen items were originally listed; the table above collapses two early WAF/auth steps into one row each where DigiCert's filing describes them as a single change. DigiCert's November 6 statement to Recorded Future News said the checklist was complete, though the Bugzilla thread itself does not carry a dated comment closing out the last two items as cleanly as the press statement implies — worth checking the live ticket rather than any single news account, including this one.

FAQ

Does this affect my TLS certificates?
No. DigiCert states that CertCentral, DigiCert ONE, and all certificate issuance/validation/revocation functions were isolated from the compromised business system and were not affected. Zero certificates were impacted.
How many customers are affected?
DigiCert has not published a number. Its own filing and customer notifications describe the identity-document exposure as a "small proportion" of the archive, without a count.
Was this a sophisticated attack?
No evidence of that has been published. The access came through a self-registration feature that lacked MFA and was never supposed to be reachable from outside DigiCert's VPN — a configuration failure following an infrastructure migration, not a disclosed exploit chain or zero-day.
Has the exposed data been misused?
DigiCert told Recorded Future News on November 6, 2026 that it has no evidence of misuse and has referred the incident to law enforcement.

Why this keeps happening

The root cause DigiCert names in its own filing is mundane and common: a network change got classified as "infrastructure," not "security," and so it skipped the review gate that exists specifically to catch new external exposure. That classification gap is why a self-registration feature built for an unrelated use case ended up attached to an archive of ID documents with no MFA in front of it. It is the same failure mode behind most of the breach post-mortems we track — a control that existed, just not on the path the actual change took.

Sources: DigiCert incident report, filed on Mozilla's CA-compliance Bugzilla tracker (bug 2084460).