An internal DigiCert business archive spent more than 500 days reachable from the public internet after a February 2025 migration. Self-registered accounts on that system skipped the MFA DigiCert required for staff, then read archived customer contacts and, for a small minority of records, customer-supplied identity documents between 27 June and 2 July 2026. According to DigiCert’s full incident report on Mozilla Bugzilla 2084460, certificate operations, CertCentral, DigiCert ONE, customer login credentials, and issued certificates were untouched. Zero certificates were affected. The damage was archive privacy, not CA issuance.

How the archive left the VPN and grew a signup path

DigiCert moved the business archive system on 4 February 2025 from a VPN-restricted segment into an externally accessible availability zone. The change was meant to improve availability. It also put an internal archive on the open internet for well over a year.

A self-registration feature intended for other products or use cases was left available on that host. Anyone who found the endpoint could create a non-staff account. According to DigiCert’s report, accounts registered through that endpoint were not subject to the multi-factor authentication DigiCert otherwise requires for staff accounts, and those accounts were assigned read-only mode by default.

Staff logins still demanded MFA. The unintended path did not. That split is the entire initial-access story: same company, same archive product family, two different enrollment rules depending on how the account was born.

DigiCert’s managed security program and internal checks eventually noticed non-DigiCert accounts. On 18 June 2026 the system went behind a WAF that blocked new external account creation. By 24 June the team had verified that external account creation had been possible. Root cause of the creation path was identified on 30 June. None of that undid the window that investigation later marked as unauthorized data access.

What the MFA-less account could actually read

Unauthorized read access ran from 27 June through 2 July 2026, according to the same Bugzilla full report. DigiCert states the access could not write records, act as a validation approver, or issue certificates. CA services stayed clean. The problem sat in archived business data.

Most of what was reachable was business contact information: names, business email addresses, phone numbers, and business addresses. A small minority of records included customer-supplied identity documents such as passports, driver’s licenses, or utility bills. DigiCert has not published an exact record count or customer count. The company describes the exposed set as a small proportion of archived data.

Authorization made the read path worse than “read-only by default” sounds. Unassigned accounts still retained permission to read archived data until a 2 July 2026 authorization patch. That patch stopped new creation abuse and disallowed archived-data access by unassigned accounts. Login MFA never got a chance to argue with a self-registered principal that was already inside with archive read rights.

Control on paper What ran on the archive Failure mode
Staff MFA Required for DigiCert staff accounts Never applied to self-registered accounts
Self-registration Left on for wrong product context Created non-staff principals without MFA
Read-only default Unassigned accounts still read archives Authorization lag until 2 July 2026 patch
VPN boundary Removed 4 Feb 2025 for availability Internet reachability for 500+ days

Later hardening closed the rest of the hole. Password resets for all business system users landed on 17 October 2026. Self-registration was deactivated across business system instances. Endpoints moved behind private-IP load balancers, tighter WAF hostname rules, and VPN expectations. Policy now requires security sign-off before internal network access changes. An external penetration test of the business system completed at the end of August 2026. DigiCert still spent months between first WAF blocks in June and public confirmation in October and early November.

DigiCert’s disclosure thread also lists adjacent CA-program incidents involving privacy or archive-data handling, including TWCA and D-Trust reports on the same Bugzilla discussion. Those are separate events DigiCert named for context, not the same intrusion path.

Why staff MFA never saw the self-registered principal

Workforce MFA only protects principals that must enroll under it. DigiCert’s staff path did. The inadvertent self-registration path minted accounts outside that rule set, on a host that no longer sat behind VPN. Once those accounts existed, archive authorization still allowed unassigned readers until the July patch. Stopping the login ceremony with stronger factors would not rewrite an authorization matrix that already granted archive reads after sign-in.

The preventable piece is enrollment on an internet-facing internal system. A verified enrollment model that refuses MFA-less self-registration on enterprise archives removes the cheap principal. Residual authorization mistakes after a legitimate session are a different control plane: least privilege, continuous review of unassigned roles, and keeping internal archives off public address space.

DigiCert’s own timeline shows how long exposure can sit quiet. Migration in February 2025. Non-staff accounts observed mid-June 2026. Confirmed reportable access mid-October. Full public write-up around 5 November 2026. Internet-reachable internal data plus an enrollment shortcut is a slow leak, not a flashy zero-day.

The defensive side of this case is covered in the related article on mfa2point0.com: prevent MFA-less self-registration on exposed internal archives.

FAQ

How did attackers get into DigiCert’s business archive?

Attackers reached DigiCert’s business archive after a 4 February 2025 migration placed the system on an internet-reachable segment and left a self-registration endpoint enabled. Accounts created through that endpoint were not subject to the MFA DigiCert required for staff accounts. DigiCert’s full incident report on Bugzilla 2084460 states those self-registered accounts defaulted to read-only mode and that unauthorized reads of archived customer data occurred from 27 June through 2 July 2026.

Did this DigiCert incident affect certificate issuance or customer certs?

No. DigiCert reported zero certificates affected and stated that certificate operations were not impacted. The access could not write archive records, act as a validation approver, or issue certificates. CertCentral, DigiCert ONE, CA services, customer credentials used for those services, and already-issued certificates were outside the compromised path.

What customer data was exposed in the DigiCert archive read?

According to DigiCert’s full incident report, most exposed material was business contact information: names, business emails, phone numbers, and business addresses. A small minority of archived records included customer-supplied identity documents such as passports, driver’s licenses, or utility bills. DigiCert has not published an exact number of records or customers.

Why didn’t DigiCert staff MFA stop the archive access?

DigiCert staff MFA applied to staff accounts. Self-registered accounts created through the inadvertent endpoint were explicitly not subject to that MFA requirement. After those accounts existed, unassigned accounts retained permission to read archived data until the 2 July 2026 authorization patch. Staff MFA never evaluated the self-registered principal at enrollment, and authorization after login sat outside the login factor.

When did DigiCert detect and close the window?

DigiCert blocked new external account creation with a WAF on 18 June 2026, verified the creation issue by 24 June, identified root cause on 30 June, and shipped the authorization patch on 2 July 2026, ending the stated data-access window. Password resets for business system users followed on 17 October 2026. Self-registration was later deactivated, and endpoints moved behind private-IP load balancers and stricter network controls before the early November public report.