← All articles

Ransomware Chains Six Zero-Days: What Stops the Attack

A six-step ransomware chain exploiting Windows zero-days — including an unpatched Defender bypass — shows why least-privilege architecture matters more than patching alone.

“A privilege escalation exploit is patched. A Defender bypass is not. The question is what your endpoint architecture does while the window is still open.”

Between April and May 2026, security researcher Nightmare-Eclipse released coordinated Windows privilege escalation, Defender bypass, and BitLocker circumvention techniques forming an active ransomware delivery chain confirmed exploited in production environments from April 10.

The Attack Chain IT Teams Are Facing

Step 1: Privilege Escalation via CVE-2026-33825

The exploit begins as an unprivileged user and escalates to NT AUTHORITY\SYSTEM via a TOCTOU flaw in Defender’s update process — patched as CVE-2026-33825 in May 2026 Patch Tuesday. The operational challenge involves confirming which endpoints actually received the fix, as deployment differs from application.

Step 2: Defender Bypass

A second technique disables Defender’s threat detection ability post-escalation. This step remains partially unaddressed with no complete Microsoft patch available.

Steps 3–6: Persistence, BitLocker Bypass, and Ransomware

With SYSTEM privileges and detection neutralized, remaining techniques establish persistence, bypass BitLocker on compromised devices, and deploy ransomware payloads.

Why Patching Alone Is Not Sufficient

Two structural realities limit patch-only responses:

  • The Defender bypass lacks a complete patch, making waiting for Microsoft fixes unviable for actively targeted organizations
  • The patch window remains perpetually open — the gap between release and confirmed remediation across estates is where exploitation typically occurs

The critical question centers on endpoint architecture effectiveness during unpatched windows or when no fix exists.

What CapaOne Does

CapaOne does not patch Windows OS vulnerabilities directly. Instead, it provides structural controls addressing different escalation sequence points.

Privilege Manager: Removing the Escalation Foundation

The most effective protection against Windows privilege escalation exploits is removing the standing local admin rights the escalation depends on. Privilege Manager enforces least-privilege by replacing always-on admin access with time-limited, policy-governed elevation through Entra ID groups.

Security Monitor: Independent Visibility When Defender Is Targeted

Security Monitor provides endpoint posture visibility operating outside Defender’s detection layer — critical when Defender becomes the attack target itself.

Application Manager: Closing Secondary Exposure

Once SYSTEM-level access is achieved, outdated third-party applications become accessible payload delivery paths. Application Manager maintains third-party applications automatically, reducing exploitable paths.

What to Do Now

Organizations should take these steps immediately:

  • Confirm CVE-2026-33825 patch posture through device-level evidence
  • Review standing local admin exposure across endpoints
  • Assess Defender dependency and activate independent posture visibility
  • Audit post-escalation exposure in third-party applications

FAQ

Is there a patch for the Defender bypass? The patch for CVE-2026-33825 exists; the Defender bypass lacks complete fixes.

What is CapaOne’s structural role? CapaOne removes escalation foundations, provides independent monitoring, and manages application vulnerabilities — it does not patch Windows OS vulnerabilities directly.

Ready to see how CapaOne handles this? Request a demo.

Book a Demo →