Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-33825: BlueHammer

Published Apr 14, 2026 · Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days7 mentions · peak 3 in a dayToday
CVSS7.8High · v3.1
EPSS6.9%94th percentile
CISA KEVYesAdded Apr 22, 2026
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2026-33825CWE-1220 · Insufficient Granularity of Access…

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.

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 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.

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 CorporationDefender Antimalware Platformapplication
Microsoft CorporationMicrosoft Defenderapplication
FAQ

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.
Activity feed

Recent activity

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

View more in app →
spaceraccoonNews · Nov 15, 2026Race Against the (Mac)hine: Local Privilege Escalation in Microsoft Defender for macOS | Spaceraccoon's BlogRace-condition vulnerability enabling local privilege escalation in Microsoft Defender for Windows. The content states that it was publicly disclosed, exploited in the wild, and patched. Its root cause helped motivate the macOS variant research.Read more ↗codebyNews · Oct 16, 2026Эксплуатация CVE до патча: MTTE -7 дней в 2026The content describes a Microsoft Defender time-of-check/time-of-use vulnerability that abuses oplocks, NTFS junctions, and the Cloud Files API to redirect Defender reads to a copy of the SAM database, exposing NTLM hashes and enabling a SYSTEM shell. It reports active exploitation and ransomware use despite a low EPSS score.Read more ↗metasploit pull requestsNews · Oct 15, 2026Add post/windows/gather/bluehammer_defender_audit (CVE-2026-33825) by anasabugaddara-ux · Pull Request #22021 · rapid7/metasploit-frameworkA vulnerability affecting Microsoft Defender, identified as BlueHammer. The content describes a read-only Metasploit audit module that compares the installed Defender platform version with a fixed build, assesses hardening posture, and checks detection events and file indicators for targeting evidence. It does not describe the vulnerability's technical mechanism or confirm exploitation in the wild.Read more ↗metasploit pull requestsNews · Oct 13, 2026WIP: Adds exploit for CVE-2026-33825 (BlueHammer) by eipoverflow · Pull Request #22013 · rapid7/metasploit-frameworkBlueHammer is presented as a Windows local privilege-escalation vulnerability through a draft Metasploit exploit pull request. The submission contains module-initialization commits, but the displayed content does not establish exploit functionality, reliability, or inclusion in the main Metasploit branch.Read more ↗
+87 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 evidence9Every report linking this CVE to a named adversary.
Associated malware18Malware families linked to this CVE, with evidence and IOCs.
Detection signatures11YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity105Community discussion across Reddit, Mastodon, and other social sources.