Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2025-53779: BadSuccessor Privilege Escalation in Windows Kerberos

Published Aug 12, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.2High · v3.1
EPSS2.9%87th percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2025-53779CWE-23 · Relative Path Traversal
Also known asbadsuccessor

CVE-2025-53779, also known as BadSuccessor, is a relative path traversal vulnerability in Windows Kerberos involving Delegated Managed Service Accounts (dMSAs) in Active Directory. An attacker who is authorized and has control of specific dMSA link and membership attributes can abuse KDC successor handling to elevate privileges over the network. The vulnerability can serve as a final stage in a multi-step Active Directory attack chain leading to domain administrator access.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can elevate an attacker’s privileges to domain administrator within an Active Directory environment. Domain administrator access can enable control of domain resources and authentication identities, facilitating broad compromise of the affected domain.

Mitigation

If you can’t patch tonight, do this now.

Limit and review delegated permissions that allow non-administrative principals to create dMSAs or modify dMSA attributes, particularly msDS-GroupMSAMembership and msDS-ManagedAccountPrecededByLink. Monitor dMSA creation and changes to dMSA membership and key-credential attributes, and investigate unexpected dMSA-to-account links. Prioritize patching systems that use dMSAs.

Remediation

Patch, then assume compromise.

Install the Microsoft security updates released in the August 2025 Patch Tuesday cycle for affected Windows Server 2025 systems. The update adds KDC-side validation requiring bidirectional links between a dMSA and its target account before the KDC issues the dMSA credential package.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Invoke-BadSuccessor.ps1This repository contains a PowerShell script, Invoke-BadSuccessor.ps1, and a README.md. The script is a fully automated exploit targeting the BadSuccessor vulnerability (CVE-2025-53779) in Windows Server 2025 Active Directory environments. It abuses misconfigured Delegated Managed Service Account (dMSA) creation rights in Organizational Units (OUs) to escalate privileges. The script identifies OUs where the attacker has CreateChild rights, creates or reuses a computer account and a dMSA, grants the attacker full control over the dMSA, and links it to a privileged account. It then provides post-exploitation instructions for forging Kerberos tickets using Rubeus, enabling impersonation of privileged users. The exploit requires the RSAT ActiveDirectory PowerShell module and is intended for use in environments where the attacker already has some level of access. The repository is well-documented, with the README providing detailed usage instructions, function descriptions, and post-exploitation steps. No external network endpoints are hardcoded; all operations are performed against the local Active Directory environment via the PowerShell AD provider and LDAP.b5null · Disclosed Nov 19, 2025 · powershell · markdown · localOperationalcve-2025-53779-kerberos_bypass_reproductionThis repository is a small standalone Python proof-of-concept exploit for CVE-2025-53779, accompanied by a detailed README. The structure is minimal: README.md documents the alleged vulnerability, affected Windows Server versions, usage examples, and post-exploitation workflow; exploit.py is the only code file and serves as the main entry point. The exploit is network-based and targets Microsoft Active Directory domain controllers exposing the Kerberos KDC service on port 88. According to the code and README, its core purpose is to craft malformed Kerberos authentication material—especially forged PA-PAC-REQUEST / PAC-related data—to trigger an authentication bypass in the KDC and obtain a TGT for an arbitrary domain user without valid credentials. The code imports Impacket Kerberos primitives (AS_REQ/AS_REP/TGS_REQ/TGS_REP, PAC structures, sendReceive, Principal, crypto helpers), indicating direct protocol-level interaction rather than simple wrapper logic. Notable capabilities described and partially visible in the code include: generating a random nonce for Kerberos requests; building a fake PAC with attacker-controlled group RIDs; forging Kerberos request padata intended to bypass PAC validation; scanning a host for Kerberos service availability; enumerating users on a target domain; and writing the resulting forged ticket to a Kirbi file for later use. The README explicitly positions the output for pass-the-ticket style follow-on activity using tools such as secretsdump.py or mimikatz. The script appears to be an exploit rather than a detector: it accepts --dc-ip, --domain, and --target-user for exploitation, plus --scan and --enum helper modes. Because it includes an exploitation workflow and produces a reusable authentication artifact, its maturity is best classified as OPERATIONAL rather than a bare conceptual PoC. No evidence suggests it belongs to a larger exploit framework such as Metasploit or Nuclei. Fingerprintable targets and artifacts are limited and mostly example-based: Kerberos port 88/TCP and 88/UDP, example DC IP 192.168.1.10, example AD domain corp.local, and output file ticket.kirbi. The repository does not embed hardcoded C2 infrastructure or external callback endpoints; instead, it is designed to communicate directly with a chosen domain controller supplied at runtime.razureink · Disclosed Jul 24, 2026 · python · markdown · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows Server 2025operating_system
FAQ

Frequently asked questions

Is CVE-2025-53779 exploited in the wild?
Yes. As of Sep 30, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-53779?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-53779, the earliest disclosed Nov 19, 2025.
Is there a patch for CVE-2025-53779?
Install the Microsoft security updates released in the August 2025 Patch Tuesday cycle for affected Windows Server 2025 systems. The update adds KDC-side validation requiring bidirectional links between a dMSA and its target account before the KDC issues the dMSA credential package.
What products are affected by CVE-2025-53779?
Microsoft Corporation Windows Server 2025.
How severe is CVE-2025-53779?
CVE-2025-53779 has a CVSS v3.1 score of 7.2 (High) and an EPSS score of 2.9% (87th percentile) as of Sep 30, 2026.
Activity feed

Recent activity

43 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+11 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity28Community discussion across Reddit, Mastodon, and other social sources.