1-minute read of a 5 min report

Certighost Lets a Domain User Impersonate a Domain Controller

By

1-minute read

What a defender needs to know

Researchers published a working proof of concept for Certighost, CVE-2026-54121, after Microsoft patched the AD CS flaw on July 14. In the tested configuration, a low-privileged domain user put an attacker-controlled host in the certificate request’s cdc attribute and named a target domain controller in rmd. The CA followed the rogue host over SMB and LDAP, accepted returned domain controller identity data, and issued a certificate that enabled PKINIT and DCSync.

The demonstrated chain required an enterprise CA, an enrollable machine template, machine-account creation rights, and the chase fallback. Microsoft has not reported active exploitation.

Apply the July update to every enterprise CA and verify the protected chase path is active. If patching must wait, test legitimate enrollment before temporarily disabling EDITF_ENABLECHASECLIENTDC.

Preserve the CA database and security logs first. Export issued-certificate and request-attribute records, then check for cdc and rmd values, machine-account requesters, and unexpected certificates carrying a domain controller identity. Correlate suspicious issuance with Kerberos evidence and DCSync telemetry from systems that are not approved domain controllers.

Closure requires patched or disabled chase paths, no unexplained domain controller certificate, contained suspicious accounts and certificates, and no unauthorized replication source. Missing CA or replication records prevents confident closure.

Primary sources