Security researchers have confirmed active, in-the-wild exploitation of three zero-day vulnerabilities affecting Microsoft Defender on modern Windows systems. The vulnerabilities, codenamed BlueHammer, RedSun, and UnDefend, were publicly disclosed by a researcher known as "Chaotic Eclipse" before official patches were available for all flaws. BlueHammer (CVE-2026-33825), a local privilege escalation (LPE) flaw, was patched in the April 2026 Patch Tuesday. However, RedSun, another critical LPE vulnerability that grants SYSTEM privileges, and UnDefend, a denial-of-service (DoS) bug, remain unpatched. Huntress Labs reports observing targeted attacks where threat actors are manually deploying these exploits to elevate privileges on compromised systems, indicating a significant and immediate threat to Windows environments.
The incident highlights the dangerous intersection of vulnerability research, contentious disclosure practices, and rapid weaponization by threat actors. A researcher, frustrated with the Microsoft Security Response Center (MSRC), publicly released proof-of-concept (PoC) exploits for three distinct vulnerabilities in Microsoft Defender. This action provided threat actors with the tools to immediately target vulnerable systems.
CVE-2026-33825): A Local Privilege Escalation (LPE) vulnerability. An attacker with low-level access can exploit this to gain SYSTEM privileges. This flaw has been patched.Researchers at Huntress Labs have observed these exploits being used in targeted attacks, not widespread automated campaigns. The attackers exhibit "hands-on-keyboard" activity, running reconnaissance commands like whoami /priv and cmdkey /list after gaining initial access, before deploying the LPE exploits to escalate their privileges. This behavior is typical of sophisticated adversaries conducting targeted intrusions.
The exploits abuse core functionalities of Microsoft Defender and its interaction with the operating system.
T1068): Both BlueHammer and RedSun are classic examples of this technique. They exploit flaws in a highly privileged process (Microsoft Defender's MsMpEng.exe service, which runs as NT AUTHORITY\SYSTEM) to execute arbitrary code with elevated permissions. The RedSun exploit reportedly abuses how Defender handles file system operations during remediation.T1562): The UnDefend vulnerability is a direct implementation of this tactic. By preventing Defender from updating, attackers can ensure that their subsequent malware payloads will not be detected by the latest signatures, significantly increasing their chances of success.T1068): The core of the BlueHammer and RedSun attacks. Attackers with initial low-privilege access (e.g., from a phishing email) can run the exploit to become SYSTEM, gaining full control of the host.T1569.002): The exploits target a legitimate and critical Windows service (Microsoft Defender) to carry out their malicious actions.The active exploitation of unpatched LPEs in a default security product is a worst-case scenario. It effectively nullifies the 'defense-in-depth' principle, as the defender itself becomes the attack vector.
The impact is critical for organizations running Windows environments. An attacker who gains any level of initial access—through phishing, a separate vulnerability, or other means—can now reliably escalate to SYSTEM-level privileges on fully patched machines using the RedSun exploit. This level of access allows them to disable other security controls, deploy ransomware, steal sensitive data, and persist within the network. The UnDefend vulnerability further compounds the risk by ensuring that the primary endpoint protection is outdated and ineffective against new threats. This forces organizations into a difficult position of needing to apply emergency workarounds or accept a high level of risk until Microsoft releases a patch.
No specific file hashes or IP addresses were provided in the source articles.
Security teams should hunt for post-exploitation activity associated with these LPEs.
whoami /privcmdkey /list%windir%\Temp\MsMpEng.exe4657HKLM\SOFTWARE\Microsoft\Windows Defender, which could indicate use of the UnDefend exploit.Detection Strategies:
MsMpEng.exe spawning unusual child processes (like cmd.exe or powershell.exe) or performing unexpected file/registry modifications.cmd.exe) being spawned as a child of MsMpEng.exe is highly suspicious and should be a high-priority alert. This is a key indicator of post-exploitation activity following a successful LPE.whoami, net user, etc.) and then a spike in MsMpEng.exe activity could indicate an attack in progress.Response Actions:
Immediate Actions (Workarounds):
MsMpEng.exe and post-exploitation commands.Strategic Controls:
New details confirm active exploitation of all three Microsoft Defender zero-days, including RedSun and UnDefend, with PoCs observed in the wild by April 16.
CISA adds CVE-2026-33825 (BlueHammer) to KEV catalog, mandating patch. Detailed exploit chain for SAM dump revealed, with initial access via FortiGate VPNs.
Apply the April 2026 security updates from Microsoft to patch CVE-2026-33825 (BlueHammer). Monitor for and apply the forthcoming patches for RedSun and UnDefend immediately upon release.
Mapped D3FEND Techniques:
Utilize EDR and behavioral analytics to detect anomalous process activities, such as MsMpEng.exe spawning command shells, which signature-based methods would miss.
Mapped D3FEND Techniques:
Implement application allowlisting to prevent the execution of the unauthorized exploit code, providing a crucial layer of defense in the absence of a patch.
Mapped D3FEND Techniques:
Enforce the principle of least privilege for user accounts. Preventing attackers from gaining initial access with an account that has permissions to write/execute files in sensitive locations can thwart the attack chain.
Given that the RedSun and BlueHammer exploits target a trusted system process (MsMpEng.exe), traditional antivirus signatures are useless. The key to detection lies in deep process analysis. Security teams must configure their EDR tools to monitor for anomalous process lineage. Specifically, create a high-severity alert for any instance where MsMpEng.exe is the parent process for cmd.exe, powershell.exe, cscript.exe, or wscript.exe. This is an extremely high-fidelity indicator of a successful LPE exploit against Defender. Furthermore, monitor for MsMpEng.exe performing file writes to unexpected locations or making suspicious registry modifications. For the UnDefend vulnerability, monitor the Defender operational logs (in the Event Viewer under Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational). A sudden cessation of events, particularly definition update events (Event IDs 2000, 2001), on a system that was previously active should trigger an investigation. This behavioral monitoring is the most effective compensating control until Microsoft releases patches for the remaining vulnerabilities.
Software Update is the primary and most definitive mitigation for these vulnerabilities. Organizations must prioritize the deployment of Microsoft's April 2026 Patch Tuesday updates to address CVE-2026-33825 (BlueHammer). This is not a routine update; it is an emergency change due to active exploitation. Use automated patch management systems to verify that the update is applied to all Windows 10, 11, and Server endpoints. For the unpatched RedSun and UnDefend vulnerabilities, the 'Software Update' strategy becomes one of proactive readiness. Security teams must establish a 'break-glass' procedure for an out-of-band patch release from Microsoft. This includes identifying a pilot group for immediate testing, having rollback plans in place, and preparing for emergency, enterprise-wide deployment outside the normal patch cycle. The risk of waiting for the next Patch Tuesday is too high given the 'hands-on-keyboard' exploitation observed in the wild. Constant monitoring of MSRC advisories is mandatory.
Exploitation of the BlueHammer vulnerability is first observed in the wild.
The April 2026 Patch Tuesday is released, patching BlueHammer (CVE-2026-33825).
Exploitation of the unpatched RedSun and UnDefend vulnerabilities begins.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.