CVE-2026-49179 is a command injection vulnerability in Windows Active Directory caused by improper neutralization of special elements used in a command. The flaw allows attacker-controlled input to be incorporated into command execution without sufficient sanitization or escaping, creating a path for arbitrary command execution. Based on the available information, the vulnerability is remotely exploitable and does not require prior authentication.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
The repository contains a single operational Python exploit, `spn_prl_exploit.py`, and a supporting README. It targets the claimed CVE-2026-49179 command-injection flaw in Active Directory's `ntdsai.dll` WriteSPNScript routine. The exploit authenticates to a supplied Domain Controller over SMB/SAMR, creates a workstation-trust account with shell metacharacters such as `&` in its machine name, and can update the account's dNSHostName to encourage SPN processing. The malicious account CN is incorporated into a DN and SPN without cmd.exe-safe escaping when the vulnerable server emits a `repadmin.exe /writespn` command. When that generated script is processed, ampersands act as command separators and attacker-controlled commands execute as SYSTEM. The script additionally has a SAMR acceptance probe that creates and removes test machine accounts for individual characters and several injection-name patterns. It requires Impacket; LDAP functionality is optional through ldap3, and SMB support is conditionally imported. There is no hardcoded victim IP address, callback host, or external URL: the Domain Controller, domain, credentials, command, trigger behavior, and optional executable payload are supplied at execution time. README references to a larger `poc/` tree do not correspond to files present in this two-file repository.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.