CVE-2026-33825: BlueHammer
- Vendor
- Microsoft Corporation
BlueHammer is a local privilege-escalation vulnerability in Microsoft Defender Antimalware Platform for Windows. Insufficiently granular access controls, combined with a time-of-check/time-of-use race and path confusion during privileged file scanning, allow a low-privileged authenticated attacker to redirect Defender's file access. Exploitation involves synchronization and filesystem redirection around scanning and Volume Shadow Copy handling, potentially exposing the Security Account Manager database and enabling escalation to SYSTEM. The vulnerability has a CVSS v3.1 score of 7.8, has been exploited in the wild, including in ransomware operations, and was patched in April 2026.
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 compromise local account password hashes and elevate an attacker from a low-privileged account to SYSTEM, giving extensive control over the affected Windows host. The resulting access can support credential theft, unauthorized system changes, and deployment of ransomware or other payloads. This is a post-compromise escalation vulnerability rather than an unauthenticated remote initial-access vector.
Mitigation
If you can’t patch tonight, do this now.
No independent preventive workaround is established in the available information; deployment of Microsoft's security update is the documented corrective measure. Monitor Defender event IDs 1116 and 1117 for BlueHammer-related detections and investigate suspected targeting. Detection monitoring does not eliminate the vulnerability.
Remediation
Patch, then assume compromise.
Apply Microsoft's April 14, 2026 security update addressing CVE-2026-33825, or a subsequent applicable update, and verify that the Microsoft Defender Antimalware Platform update installed successfully. The fix strengthens access controls on sensitive platform paths and improves identification and validation of processes interacting with core security components. Exact affected-version ranges and the minimum fixed Defender platform build are not available in the supplied information.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 9 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
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.
References
Frequently asked questions
- Is CVE-2026-33825 exploited in the wild?
- Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 22, 2026.
- Is there a public exploit for CVE-2026-33825?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-33825, the earliest disclosed May 2, 2026.
- Is there a patch for CVE-2026-33825?
- Apply Microsoft's April 14, 2026 security update addressing CVE-2026-33825, or a subsequent applicable update, and verify that the Microsoft Defender Antimalware Platform update installed successfully. The fix strengthens access controls on sensitive platform paths and improves identification and validation of processes interacting with core security components.
- What products are affected by CVE-2026-33825?
- Microsoft Corporation Defender Antimalware Platform and Microsoft Corporation Microsoft Defender.
- How severe is CVE-2026-33825?
- CVE-2026-33825 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 6.9% (94th percentile) as of Nov 17, 2026.
Recent activity
218 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.