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 changeEFF warns ambient surveillance devices expand privacy risks for bystanders DeadlineFrench court orders DNS resolver Quad9 to block sites, prompting its withdrawal from France CriticalZero‑Day SignDrop Exploit Escalates to SYSTEM and Bypasses Windows Defender RansomwareBYOD Ransomware Gang Claims to Encrypt Vanderbilt University Databases and Steal Over 1 Million Records Rule changeAmended California Consumer Privacy Act (Prop. 24) set to become effective Jan 1 2026 CriticalPostgreSQL 18.7‑14.25 Update Patches 52 Vulnerabilities, Ends Support for PostgreSQL 14
Updated 02:04 UTC All intelligence →
Digital Trust PractitionersAssociation of Digital Trust Practitioners · TrustPractitioners.org
EN
JoinJoin
BREACH WATCH BRIEF Critical 👤 Vulnerability

N‑able ‘4EverAble2Shell’ Zero‑Day Exploited Hours After PoC Release, Compromising 21 RMM Servers

Researchers observed active exploitation of N‑able’s newly disclosed 4EverAble2Shell zero‑day, granting root access to N‑central appliances and installing Monero miners on 21 servers across six countries. The incident highlights the need for robust vulnerability‑management controls and immediate disabling of legacy APIs.

ADTP Breach Watch · November 12, 2026 · BleepingComputer
SeverityCritical
Type👤 Vulnerability
ConfidenceHigh
ReportedNov 12, 2026
Technology & SaaS Managed Service Providers (MSPs) using N‑able N‑central Vulnerability Exploit Zero-Day Exploit

What happened

A zero‑day chain (CVE‑2026‑90436 + N‑central privilege escalation) was publicly released and exploited within hours, leading to root compromise of 21 N‑central servers and deployment of cryptocurrency miners.

Why it matters for trust and compliance

  • The breach tests the Vulnerability Management control objective—organizations must detect, assess, and remediate critical flaws quickly to maintain audit‑ready evidence.
  • Map vulnerability‑management processes to the VCF control for timely patching and evidence collection.
  • Demonstrate continuous monitoring of legacy API usage as part of audit‑ready control evidence.

Who is affected

Managed Service Providers (MSPs) using N‑able N‑central

Recommended actions

  1. Disable Legacy API on all N‑central appliances.
  2. Implement continuous monitoring for the documented IOCs.
  3. Accelerate patch‑management timelines for critical CVEs.
  4. Audit the Vulnerability Management control and collect supporting evidence.

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.

Explore the mapFollow Regulatory Watch
  • 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.