Live threats
HighUnpatched Check Point Gateways Exploited via PHP2Shell, Granting Root Access and Enabling Wiper Attacks BreachUS DOJ Seizes $1.2 B Stolen from Binance Theft and Disrupts North Korean ‘FaceStealer’ Social‑Engineering Tool Rule changeFederal Register limits automated scraping of its sites, directing users to APIs DeadlineFarm Credit Administration amends employee payroll system of records under Privacy Act, effective Nov 24, 2026 CriticalCritical Use‑After‑Free RCE (CVE‑2026‑109618/109619) in Siemens RUGGEDCOM APE1808 Industrial Routers BreachScreenConnect Attacks Compromise ≥ 288 Endpoints in 48 Organizations via Rogue Remote‑Access Clients Rule changeFPF launches four-part virtual roundtable series on Agentic AI, privacy risks and PETs CriticalZero‑Day SignDrop Exploit Escalates to SYSTEM and Bypasses Windows Defender
Updated 08:43 UTC All intelligence →
BREACH WATCH BRIEF Critical 👤 Vulnerability

Zero‑Day SignDrop Exploit Escalates to SYSTEM and Bypasses Windows Defender

A new Windows zero‑day (SignDrop) lets an unprivileged user gain SYSTEM rights by abusing the CLFS authentication mitigation and tricking Windows Defender into creating signed files. The flaw highlights the importance of strict privileged‑access controls and continuous verification of security‑control configurations.

SeverityCritical
Type👤 Vulnerability
ConfidenceHigh
ReportedNov 13, 2026
Other / Unknown Enterprises running Windows 10/11 or Windows Server 2025 with CLFS mitigation enabled Vulnerability Exploit

What happened

Researcher Chaotic Eclipse released a PoC for SignDrop, a local‑privilege‑escalation bug in the CLFS driver that can be leveraged to force Windows Defender to create a signed file with SYSTEM privileges, effectively bypassing antimalware tamper‑protection.

Why it matters for trust and compliance

  • The issue underscores the need for robust privileged‑access management and continuous monitoring of mitigation settings to maintain audit‑ready control assurance.
  • Validate and document the configuration of CLFS authentication as part of privileged‑access control evidence.
  • Monitor for anomalous antimalware process activity to provide defensible evidence of control effectiveness.

Who is affected

Enterprises running Windows 10/11 or Windows Server 2025 with CLFS mitigation enabled

Recommended actions

  1. Check the CLFS authentication mode registry key and ensure it is set to 2 or 3.
  2. Apply Microsoft’s upcoming patch promptly and track security advisories.
  3. Enforce least‑privilege policies and audit elevation‑of‑privilege events.
  4. Deploy endpoint monitoring for suspicious calls to ServerMpUpdateEngineSignature.

Regulations library

Every US state privacy law, on one map

24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.

  • In force
  • Coming into force
  • Sector laws
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA UT CO NE MO KY WV VA MD DE AZ NM KS AR TN NC SC DC OK LA MS AL GA HI TX FL

Get the Breach Digest

The incidents that matter for your vendors and your data, analyzed for practitioners, in one email.