CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-07-09
ROUTINECVE-2026-50656updatedNATOA2vulnerability

CVE-2026-50656: Microsoft Defender engine 'RoguePlanet' local privilege escalation now patched; NCSC-CH tracks the ongoing 'Nightmare Eclipse' zero-day series

Microsoft ships the engine fix for RoguePlanet (CVE-2026-50656), the Defender SYSTEM-level LPE NCSC-CH has tracked with a public PoC since June

Defender actions

  • On WSUS-gated, air-gapped, offline or OT-adjacent Windows estates where Defender engine updates are deferred or pinned, verify the installed Malware Protection Engine build is ≥ 1.1.26080.3, which also closes the ShieldBreak bypass (CVE-2026-69414) of this fix, rather than assuming auto-update reached it.

Analysis

NCSC-CH's running tracker on the "Nightmare Eclipse" (aka Chaotic Eclipse) researcher's 2026 zero-day PoC series was updated on 2026-07-09 to record that a CVE has been assigned to RoguePlanet: CVE-2026-50656, a local privilege-escalation vulnerability (CWE-59, improper link resolution before file access / "link following") in the Microsoft Malware Protection Engine that underpins Microsoft Defender, System Center Endpoint Protection and Microsoft Security Essentials (NCSC-CH, 2026-07-09) (Microsoft MSRC, 2026-07-08). The researcher first disclosed RoguePlanet as an unpatched zero-day on 2026-06-09, Patch Tuesday, describing a race condition in Defender that lets a local attacker "execute arbitrary code or spawn a command shell with SYSTEM-level privileges", at which point NCSC-CH logged its status as "Proof of Concept Available, no patch available" (NCSC-CH, 2026-07-09). Microsoft's own record shows the CVE was published 2026-06-16 (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N, rated "Exploitation More Likely", exploitation status "No") and remained without a fix for over three weeks; a revision dated 2026-07-08 confirms Microsoft has now shipped an engine update that closes it: last vulnerable Malware Protection Engine build 1.1.26050.11, first fixed build 1.1.26060.3008 (Microsoft MSRC, 2026-07-08).

NCSC-CH later recorded that a proof of concept dubbed ShieldBreak allegedly bypasses this fix; Microsoft tracks it as CVE-2026-69414 (NCSC-CH, 2026-07-09) and lists engine 1.1.26080.3 as the first build that addresses it (Microsoft Security Response Center, CVE-2026-69414).

Cited evidence

Microsoft has released an update to the Microsoft Malware Protection Engine that addresses the vulnerability identified by CVE-2026-50656.

Microsoft is aware of an elevation of privilege in the Microsoft Malware Protection Engine in Microsoft Defender publicly referred to as

Microsoft Security Response Center

Updates2

Correction

Neither Microsoft's advisory nor NCSC-CH's tracker describes the exploitation mechanism beyond link following and a race condition, so the earlier triage guidance on symlink races against scanned files and on the engine's child processes is withdrawn. NCSC-CH has since recorded that a proof of concept dubbed ShieldBreak allegedly bypasses this fix, tracked by Microsoft as CVE-2026-69414 (NCSC-CH, 2026-07-09); Microsoft lists engine 1.1.26080.3 as the first build that addresses it (Microsoft Security Response Center, CVE-2026-69414). The priority moves from notable to routine: the flaw is local and the engine fix installs automatically. A pinned estate should therefore verify that build rather than the RoguePlanet fix alone.

Improvement

Microsoft identifies the vulnerable engine as mpengine.dll and says Defender runs on all supported versions of Windows, so every Windows host with Defender enabled was in scope until its engine reached 1.1.26060.3008; hosts with Defender disabled are not in an exploitable state (Microsoft MSRC, 2026-07-08).

Sources3

Revision history

  1. Published 2026-07-09T2009Z-intel
  2. Correction 2026-10-11T1307Z-audit

    Adds references to the earlier entry that shares this CVE and to the ShieldBreak entry on the alleged bypass of this fix, and a source rating. The Triage line described a scan race and an engine process lineage that neither source gives and is removed, and the second evidence quote is replaced with Microsoft's own description of the flaw. The summary and analysis record NCSC-CH's note of the ShieldBreak bypass (CVE-2026-69414), the engine and product details are cited to Microsoft, the estate examples are marked as the entry's own reading, a tracking action that called the flaw fixed is dropped, and the priority moves from notable to routine for a local flaw whose engine fix installs automatically. The action's engine floor rises to 1.1.26080.3, the build Microsoft lists as fixing the ShieldBreak bypass, and the auto-update cadence follows Microsoft's wording. The disclosure and public-PoC date is 2026-06-09, Patch Tuesday.

    Changed: references classification body summary priority evidence actions sources

  3. Improvement 2026-10-21T0800Z-audit

    Microsoft's record places the flaw in mpengine.dll, which Defender runs on all supported versions of Windows, so every Windows host with Defender enabled was in scope until engine 1.1.26060.3008, while hosts with Defender disabled are not exploitable.

    Changed: title body

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.