Certighost: The Windows AD CS Flaw That Turned Ordinary Users into Domain Controllers

Listen to this Post

Featured ImageIntroduction – A Wake-Up Call for Windows Enterprise Security

Microsoft’s Active Directory infrastructure has long been considered the backbone of enterprise authentication, identity management, and access control. Organizations across the world rely on Active Directory Certificate Services (AD CS) to issue digital certificates that securely authenticate users, computers, and services. However, a newly disclosed vulnerability known as Certighost (CVE-2026-54121) has revealed how a trusted component of Windows infrastructure could be abused to completely compromise an Active Directory domain.

The release of a public proof-of-concept (PoC) exploit significantly raises the urgency of this vulnerability. While Microsoft already addressed the flaw during the July 2026 Patch Tuesday updates, the availability of exploit code means attackers now have a practical blueprint for reproducing the attack against unpatched environments.

This vulnerability demonstrates that even low-privileged authenticated users can potentially escalate privileges to one of the highest levels inside a Windows domain. That makes Certighost one of the most significant Active Directory privilege escalation vulnerabilities disclosed in 2026.

The Discovery of CVE-2026-54121

Security researchers H0j3n and Aniq Fakhrul responsibly disclosed the vulnerability to Microsoft on May 14, 2026. Microsoft investigated the issue and included a security fix in its July 2026 Patch Tuesday release.

The vulnerability received the identifier CVE-2026-54121 and affects Active Directory Certificate Services (AD CS).

According to Microsoft, an authenticated attacker can manipulate machine account attributes and obtain a certificate capable of authenticating as another machine using PKINIT (Public Key Cryptography for Initial Authentication in Kerberos).

If that targeted machine happens to be a Domain Controller, the attacker effectively gains the ability to authenticate as the Domain Controller itself.

That level of access opens the door to complete domain compromise.

Why Active Directory Certificate Services Matters

Active Directory Certificate Services is

It performs several critical security functions including:

Issuing authentication certificates

Supporting smart-card authentication

Enabling secure communications

Providing certificate-based Kerberos authentication

Managing digital identities across enterprise environments

Because AD CS is deeply trusted inside Active Directory, any weakness within its validation logic can have catastrophic consequences.

Certighost is exactly that type of weakness.

Understanding the Vulnerability

The flaw exists within an optional certificate enrollment fallback mechanism that researchers call the “Chase” process.

During certificate enrollment, two request attributes may be supplied:

cdc (Client DC) – Specifies which server the Certificate Authority should contact.

rmd (Remote Domain) – Specifies which account should be searched.

Normally, these values help the Certificate Authority locate identity information.

Unfortunately, prior to

Instead, the Certificate Authority trusted whatever server the client specified.

That single design flaw became the foundation of the entire attack chain.

How Attackers Exploit Certighost

The exploitation process is surprisingly elegant.

An attacker first creates a machine account.

This is normally allowed because Active

That machine account becomes a legitimate security principal.

Next, the attacker builds fake infrastructure by hosting rogue:

SMB services

LDAP services

LSA services

Instead of pointing the Certificate Authority toward the real Domain Controller, the attacker points it toward these fake services.

Because the vulnerable Certificate Authority fails to validate the destination server, it trusts the attacker’s responses.

The rogue services then claim to represent the targeted Domain Controller account.

The Certificate Authority accepts the information and issues a valid authentication certificate.

That certificate now represents the Domain Controller.

From Low Privilege to Complete Domain Compromise

Once the forged certificate is issued, the attack escalates rapidly.

The released certighost.py proof-of-concept automates the process by:

Performing PKINIT authentication

Requesting Kerberos credentials

Saving them into a .ccache file

Extracting the Domain Controller NT hash

With those credentials, attackers can immediately perform advanced Active Directory attacks.

Researchers demonstrated using

DCSync allows attackers to replicate password data directly from Active Directory.

Among the extracted secrets is the highly valuable:

krbtgt account hash

Possession of the krbtgt hash enables attackers to forge Golden Tickets, granting persistent and virtually unrestricted access throughout the domain.

At that stage, the organization has effectively lost control of its Active Directory environment.

Microsoft’s Security Fix

Microsoft corrected the vulnerability during the July 2026 Patch Tuesday release.

The updated Certificate Authority now performs two critical validation steps.

First, it confirms that the server specified in the cdc attribute genuinely maps to a legitimate Domain Controller inside Active Directory.

Second, it verifies that the identity returned during the chase process matches the expected account.

These additional verification steps eliminate the trust issue that enabled the attack.

Organizations that install

Temporary Mitigation for Unpatched Systems

For organizations unable to deploy the July security updates immediately, researchers recommend disabling the optional Chase fallback mechanism.

Use the following commands:

certutil -setreg policyditFlags -EDITF_ENABLECHASECLIENTDC

Restart-Service CertSvc -Force

This mitigation disables the vulnerable fallback behavior.

However, the researchers clearly emphasize that this workaround has not been extensively validated in production environments.

Administrators should treat it only as a temporary emergency measure.

Installing

Deep Analysis

The Certighost vulnerability highlights a recurring security lesson in enterprise environments: trust relationships are often the weakest link. AD CS assumed that any server identified through the cdc parameter was trustworthy, creating an opportunity for attackers to insert rogue infrastructure into the certificate enrollment workflow.

Attack Flow

Authenticated User


Create Machine Account


Deploy Rogue SMB/LDAP/LSA Services


Manipulate cdc + rmd Attributes


Certificate Authority Contacts Rogue Server


Fake Identity Returned


Certificate Issued for Domain Controller


PKINIT Authentication


Kerberos Ticket (.ccache)


Extract NT Hash


DCSync Attack


Steal krbtgt Hash


Full Active Directory Compromise

Detection Commands

Get-HotFix | Where-Object {$_.Description -match "Security"}
certutil -config - -ping
Get-ADComputer -Filter 

Get-WinEvent -LogName Security

repadmin /showrepl

Defensive Recommendations

Deploy the July 2026 Microsoft security updates across all Domain Controllers and Certificate Authorities.

Monitor certificate enrollment requests for unusual cdc or rmd attribute values.

Audit machine account creation and consider reducing or disabling the default ms-DS-MachineAccountQuota where operationally feasible.

Watch for unexpected PKINIT authentication events originating from newly created machine accounts.

Continuously validate AD CS configurations through red-team exercises and attack simulations to uncover trust-based weaknesses before adversaries do.

What Undercode Say:

The publication of the Certighost proof-of-concept changes the threat landscape considerably. While the vulnerability itself was responsibly disclosed and patched, public exploit code dramatically lowers the barrier for attackers targeting organizations that have delayed patching.

One of the most concerning aspects is that the attack begins with an authenticated but low-privileged user. Many organizations assume internal users represent a lower risk than external attackers, yet Certighost demonstrates how a single compromised account can become the starting point for total domain takeover.

The attack also emphasizes how dangerous implicit trust can be inside enterprise identity systems. Rather than exploiting memory corruption or bypassing cryptographic protections, the attacker abuses a logical validation weakness in the certificate enrollment process. This makes the exploit reliable and difficult to detect using traditional endpoint-focused defenses.

Another important observation is the role of machine accounts. The default ms-DS-MachineAccountQuota setting, intended for administrative convenience, becomes an enabler for privilege escalation in this scenario. Organizations should carefully evaluate whether default configurations still align with modern threat models.

The exploit chain also highlights the value of offensive security tools. By combining certificate abuse, PKINIT, Kerberos credential extraction, and DCSync techniques, attackers can chain together legitimate Windows features into a highly effective compromise path.

Detection remains a challenge because much of the activity leverages trusted protocols such as LDAP, SMB, Kerberos, and AD CS. Security teams relying solely on signature-based detection or endpoint antivirus may overlook these actions.

Behavioral monitoring becomes essential. Certificate issuance anomalies, unusual machine account creation, unexpected PKINIT usage, and replication requests should all be considered high-value telemetry sources.

Identity infrastructure deserves the same level of continuous monitoring as internet-facing systems. Certificate Authorities, Domain Controllers, and authentication services are now prime targets for sophisticated adversaries.

Organizations should also review whether legacy AD CS configurations remain necessary. Features designed for compatibility years ago may introduce unnecessary attack surfaces today.

Finally, Certighost serves as another reminder that Patch Tuesday updates often contain fixes for vulnerabilities that quickly become weaponized once technical details are published. Delaying deployment increases the window of exposure and provides attackers with an opportunity to exploit well-understood weaknesses.

✅ Fact: Microsoft patched CVE-2026-54121 during the July 2026 Patch Tuesday release. This aligns with Microsoft’s published security updates and the researchers’ disclosure timeline.

✅ Fact: The exploit abuses Active Directory Certificate Services by manipulating certificate enrollment through the Chase mechanism. This behavior is consistent with the technical explanation provided by the researchers.

✅ Fact: Public proof-of-concept code demonstrates that successful exploitation can lead to PKINIT authentication, DCSync attacks, and extraction of the krbtgt account credentials, making domain-wide compromise a realistic outcome for vulnerable environments.

Prediction

(+1) Microsoft and enterprise security vendors will place greater emphasis on strengthening validation within Active Directory Certificate Services and expanding monitoring capabilities for certificate-based authentication. Organizations are also likely to accelerate hardening of AD CS deployments, reduce unnecessary trust relationships, and review default Active Directory configurations such as ms-DS-MachineAccountQuota. At the same time, red-team exercises and continuous attack simulation focused on identity infrastructure will become increasingly common as defenders recognize that certificate services have become one of the most attractive targets for modern attackers.

🕵️‍📝Let’s dive deep and fact‑check.

🎓 Live Courses & Certifications:

Join Undercode Academy for Verified Certifications

🚀 Request a Custom Project:

Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]
💎 Smart Architecture | 🛡️ Secure by Design | ⭐ Trusted by Thousands

References:

Reported By: www.bleepingcomputer.com
Extra Source Hub (Possible Sources for article):
https://www.reddit.com/r/AskReddit
Wikipedia
OpenAi & Undercode AI

Image Source:

Unsplash
Undercode AI DI v2

🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]

💬 Whatsapp | 💬 Telegram

📢 Follow UndercodeNews & Stay Tuned:

𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon | 📺Youtube