Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-69414: ShieldBreak

Published Aug 14, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS7.8High · v3.1
EPSS1.4%73rd percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2026-69414CWE-362

ShieldBreak (CVE-2026-69414) is a local elevation-of-privilege vulnerability in the Microsoft Malware Protection Engine used by Microsoft Defender. It bypasses the remediation for RoguePlanet (CVE-2026-50656) by abusing privileged file processing involving Cloud Filter API hooking during cloud-file hydration and Defender file-handling races. A low-privileged local attacker can exploit the vulnerability to obtain SYSTEM privileges without user interaction. Engine versions earlier than 1.1.26080.3 are identified as affected; Microsoft released that version to address ShieldBreak in September 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 allows a low-privileged local attacker to obtain SYSTEM privileges, compromising the confidentiality, integrity, and availability of the affected endpoint. This can enable access to protected information, modification of system resources, and interference with services or security controls. The vulnerability has a reported CVSS v3 base score of 7.8.

Mitigation

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

Restrict untrusted local code execution through AppLocker or Windows Defender Application Control, and limit unnecessary interactive access to sensitive endpoints. Monitor unexpected privileged Defender file operations and correlate them with preceding low-privileged process activity. These controls reduce exposure or aid detection but do not replace the engine update.

Remediation

Patch, then assume compromise.

Update the Microsoft Malware Protection Engine to version 1.1.26080.3 or a later supported release. Enable automatic malware-engine updates and verify the installed engine version using Microsoft's guidance in Knowledge Base Article 2510781; installation of Windows cumulative updates alone should not substitute for engine-version verification. ShieldCrash is a subsequently disclosed bypass of this remediation, so the ShieldBreak update should not be treated as proof that all related exploitation paths have been eliminated.

Public exploits

Exploits

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

View more in app →
ShieldCrashShieldCrash is a small Visual Studio C++20 console-project repository centered on the 52 KB ShieldCrash.cpp source file. It claims a residual Microsoft Defender Antivirus vulnerability related to CVE-2026-69414 (“ShieldBreak”) and implements a local proof of concept for reading an arbitrary file through a SYSTEM-context Defender processing path. The visible tail of the source derives an output filename from the requested input path and a GUID, creates a destination file, uses file mappings and memmove to copy the obtained content, and deletes a staged object with NtDeleteFile. The source imports native Windows APIs and libraries including ntdll, Cloud Files (CldApi), Task Scheduler, KTM, Shlwapi, and Winsock; named synchronization objects and variables indicate a WebDAV-related staging/coordination component. No fixed remote host, URL, IP address, or command-and-control endpoint is visible in the supplied code. The project references ZIP and DLL resources (eicar_com.zip and Warden.dll), although the declared ShieldCrash.rc resource script and those two input artifacts are absent from the supplied eight-file archive, so a clean build may be incomplete. This is not a detection-only script and contains no reverse-shell or SYSTEM code-execution payload; its stated and code-supported objective is local data disclosure.c++ · xml · localOperationalshieldbreakShieldBreak is a standalone Visual Studio C++20 console project, not a known exploitation framework module. Its primary implementation is ShieldBreak.cpp (about 47 KB); the remaining listed files are Visual Studio solution/project metadata, a resource-ID header, README, and license. The project is configured for Win32 and x64 Debug/Release builds and links against ntdll, CldApi, onecore, and Task Scheduler libraries. The source defines Microsoft Defender-related internal data types and uses Windows Cloud Files APIs, COM Task Scheduler interfaces, Windows Error Reporting task execution, resource extraction, and a named pipe. It embeds or expects ZIP and DLL resources and cleans up the synchronization root, WER files/directories, scan target, and pipe after execution. No remote host, URL, IP address, DNS name, or external C2 endpoint is present in the supplied code. The project metadata references ShieldBreak.rc plus several binary/resource inputs that are absent from the eight-file listing, meaning the repository as provided may not build without those missing artifacts. The README attributes the technique to CVE-2026-50656 and claims a Defender patch bypass, but the claim and the behavior of the unavailable embedded DLL cannot be independently verified from the supplied contents.cpp · xml · localOperational
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 CorporationMalware Protection Engineapplication
FAQ

Frequently asked questions

Is CVE-2026-69414 exploited in the wild?
Yes. As of Nov 19, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-69414?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-69414.
Is there a patch for CVE-2026-69414?
Update the Microsoft Malware Protection Engine to version 1.1.26080.3 or a later supported release. Enable automatic malware-engine updates and verify the installed engine version using Microsoft's guidance in Knowledge Base Article 2510781; installation of Windows cumulative updates alone should not substitute for engine-version verification.
What products are affected by CVE-2026-69414?
Microsoft Corporation Malware Protection Engine.
How severe is CVE-2026-69414?
CVE-2026-69414 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 1.4% (73rd percentile) as of Nov 19, 2026.
Activity feed

Recent activity

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

View more in app →
thecyberexpress com vulnerabilitiesNews · Nov 13, 2026SignDrop Zero-Day Exploit Abuses CLFS To Gain AccessA previously disclosed vulnerability associated with MSNightmare's Windows and Defender research, mentioned as background. The content identifies its name, CVE, and August disclosure timing, but provides no specific technical details, patch status, or confirmed exploitation history.Read more ↗the hacker newsNews · Nov 12, 2026New SignDrop Zero-Day Exploit Turns Windows CLFS Security Feature Into SYSTEM AccessAn earlier Microsoft Defender bypass associated with the researcher's ShieldBreak exploit, mentioned as background. The article characterizes the earlier Defender exploits collectively as targeting race conditions in file handling, but does not provide detailed mechanics or patch status for ShieldBreak.Read more ↗tenable nessus pluginsNews · Oct 9, 2026Windows Defender <= 1.1.26070.7 Elevation of Privilege (Shield... | Tenable®A local elevation-of-privilege vulnerability in Microsoft Defender's Malware Protection Engine, affecting versions through 1.1.26070.7. The listed CVSS v3 score is 7.8, with low privileges required, no user interaction, and high confidentiality, integrity, and availability impacts. Nessus identifies potentially affected installations using the application's self-reported version rather than testing exploitation.Read more ↗uganda certNews · Oct 6, 2026Microsoft Officially Assigns CVE to ShieldBreak Zero-Day as Patch Development Confirmed (CVE-2026-69414) | Uganda National Computer Emergency Response Team-National CertAn elevation-of-privilege vulnerability in the Microsoft Malware Protection Engine, rated CVSS 7.8. The content describes it as a complete bypass of the RoguePlanet patch that grants SYSTEM privileges on fully patched Windows systems. Microsoft assessed exploitation as more likely and was developing a patch. The statement about confirmed exploitation concerns the researcher's prior vulnerabilities, not ShieldBreak.Read more ↗
+29 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 activity69Community discussion across Reddit, Mastodon, and other social sources.