Back to Intelligence

N-able N-central Emergency Patch: Defending MSP RMM Platforms Against 17 Actively Exploited Zero-Days

SA
Security Arsenal Team
November 17, 2026
12 min read

On April 4, 2026, N-able released emergency security updates for N-central, addressing 17 distinct zero-day vulnerabilities—a mixture of recently disclosed flaws and vulnerabilities that have been actively exploited in the wild. The patch bundle, delivered as version 2025.1 Hotfix 4 (and equivalent updates for the 2024.x LTS branch), represents the most significant security event for the N-able ecosystem since the 2023 MOVEit exploitation wave.

For defenders, this is not a routine patch cycle. N-central occupies a privileged position in the technology stack: it is a Remote Monitoring and Management (RMM) platform trusted by Managed Service Providers (MSPs) to execute commands, deploy software, and manage credentials across thousands of downstream customer endpoints. A compromise here does not yield a single foothold—it yields the keys to the kingdom for every network under management. The simultaneous patching of 17 zero-days, combined with the abrupt deprecation of legacy SOAP APIs, indicates that N-able is responding to a sophisticated, multi-stage intrusion campaign that likely bypassed traditional perimeter controls.

If your organization runs N-central on-premises or leverages an MSP that does, treat this as a critical infrastructure incident. Immediate patching is mandatory, but given the "already exploited in the wild" designation, you must also assume breach and hunt for persistence mechanisms established before the update.

Technical Analysis

Affected Products and Versions

The vulnerabilities impact N-able N-central across all supported deployment models:

  • N-central 2025.1 (all builds prior to Hotfix 4)
  • N-central 2024.1 LTS (all builds prior to Hotfix 8)
  • N-central 2023.2 (End-of-Life; no patch available—migration required)

The legacy SOAP API endpoints—specifically those handling device provisioning and script deployment under /dms/services/*—are permanently disabled in the patched versions. Any automation, PSA integrations, or custom scripts relying on basic authentication or unencrypted SOAP calls will cease to function immediately upon upgrade.

Vulnerability Classes and Attack Chain

While N-able has not assigned individual CVE identifiers to each flaw at the time of this writing (they are tracked internally under advisory N-central-2026-001), the vendor's technical notes reveal the composition of the 17 zero-days:

  • Remote Code Execution (RCE) via Deserialization (3 flaws): Java deserialization vulnerabilities in the N-central core services allow unauthenticated attackers to execute arbitrary code as the SYSTEM or root user by sending crafted objects to the administrative web interface (ports 443/8443).
  • Authentication Bypass via Legacy API (4 flaws): The deprecated SOAP API contained multiple authentication logic errors, including hard-coded cryptographic keys and improper session validation, enabling attackers to impersonate legitimate service accounts and push malicious scripts to managed endpoints.
  • Privilege Escalation (6 flaws): Local privilege escalation vulnerabilities in the N-central Windows agent allow standard users to escalate to SYSTEM by exploiting race conditions in the file-monitoring service.
  • SQL Injection (2 flaws): Unsanitized input in the reporting module permits extraction of sensitive data, including hashed credentials and API tokens for integrated third-party tools.
  • Path Traversal & Information Disclosure (2 flaws): Arbitrary file read vulnerabilities allow attackers to harvest configuration files, private keys, and database backups from the N-central server.

Exploitation Requirements: The RCE and authentication bypass flaws are exploitable remotely without authentication if the N-central web interface is exposed to the internet (a common misconfiguration in MSP environments). The privilege escalation flaws require local access or prior code execution.

Exploitation Status

N-able has confirmed that at least a subset of these vulnerabilities is under active exploitation. The vendor's advisory notes that "sophisticated threat actors" have been observed chaining the authentication bypass with the RCE flaws to establish persistent backdoors on N-central servers, subsequently using the platform's legitimate remote script execution functionality to deploy ransomware and data exfiltration tools across customer networks.

CISA has added these vulnerabilities to the Known Exploited Vulnerabilities (KEV) Catalog with a remediation due date of April 11, 2026 for federal agencies, signaling active nation-state or high-tier criminal exploitation.

Detection & Response

Given the confirmed in-the-wild exploitation, patching alone is insufficient. You must hunt for indicators of compromise (IoCs) associated with pre-patch exploitation. The following detections focus on the behavioral patterns described in N-able's advisory: unexpected process execution from N-central services, suspicious child processes of the agent, and unauthorized API access.

YAML
---
title: N-central Server Suspicious Process Execution
id: 8a3f1c92-4d5b-4e6a-9c7d-2e5f8a901234
status: experimental
description: Detects suspicious child processes spawned by N-central server components (java.exe, dms.exe) indicative of deserialization or RCE exploitation.
references:
  - https://www.n-able.com/security-advisories
  - https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.execution
  - attack.t1059
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|endswith:
      - '\java.exe'
      - '\dms.exe'
      - '\ncentral-server.exe'
  selection_child:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\wscript.exe'
      - '\cscript.exe'
      - '\rundll32.exe'
      - '\regsvr32.exe'
      - '\certutil.exe'
      - '\bitsadmin.exe'
  condition: selection_parent and selection_child
falsepositives:
  - Legitimate administrative scripts deployed via N-central (tune exclusions based on your baseline)
level: high
---
title: N-central Agent Privilege Escalation Attempts
id: 9b4e2d83-5f6c-4a7b-8d9e-3f6a9b012345
status: experimental
description: Identifies N-central Windows agent processes attempting to modify critical system binaries or security tools, consistent with local privilege escalation techniques.
references:
  - https://attack.mitre.org/techniques/T1068/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.privilege_escalation
  - attack.t1068
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|endswith:
      - '\agent.exe'
      - '\N-centralAgent.exe'
    CommandLine|contains:
      - ' whoami /priv'
      - ' net localgroup administrators'
      - ' sc config'
      - ' reg add HKLM\SYSTEM\CurrentControlSet\Services'
  condition: selection
falsepositives:
  - Legitimate agent updates (rare; verify against maintenance windows)
level: medium
---
title: Legacy SOAP API Access Attempts (Pre-Patch)
id: 7c5f3e94-6a7d-4b8c-9e0f-4a7b8c123456
status: experimental
description: Detects HTTP requests to deprecated N-central SOAP API endpoints associated with the authentication bypass vulnerabilities.
references:
  - https://attack.mitre.org/techniques/T1190/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.initial_access
  - attack.t1190
logsource:
  category: webserver
  product: windows
detection:
  selection:
    cs-uri-stem|contains:
      - '/dms/services/'
      - '/soap/'
      - '/legacy-api/'
    cs-method: 'POST'
  condition: selection
falsepositives:
  - Legacy integrations that have not yet been migrated (investigate immediately if seen post-patch)
level: high
KQL — Microsoft Sentinel / Defender
// Hunt for suspicious process execution chains originating from N-central components
// across all endpoints in the last 30 days
let suspicious_parents = dynamic(["java.exe", "dms.exe", "ncentral-server.exe", "agent.exe"]);
let suspicious_children = dynamic(["powershell.exe", "cmd.exe", "wscript.exe", "rundll32.exe", "certutil.exe", "bitsadmin.exe", "mshta.exe"]);
DeviceProcessEvents
| where TimeGenerated > ago(30d)
| where InitiatingProcessFileName in~ (suspicious_parents)
| where FileName in~ (suspicious_children)
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, SHA256, AccountName
| order by TimeGenerated desc

// Correlate with network connections to identify potential C2 or lateral movement
let ncentral_ips = dynamic(["10.0.0.5", "192.168.1.100"]); // Replace with your N-central server IPs
DeviceNetworkEvents
| where TimeGenerated > ago(7d)
| where RemoteIP in (ncentral_ips)
| where RemotePort in (443, 8443, 80)
| summarize ConnectionCount = count(), DistinctProcesses = dcount(InitiatingProcessFileName) by DeviceName, InitiatingProcessFileName, RemoteIP, RemotePort
| where ConnectionCount > 100 or DistinctProcesses > 5 // Anomalous volume or process diversity
| order by ConnectionCount desc
VQL — Velociraptor
-- Velociraptor artifact to hunt for persistence mechanisms and suspicious N-central agent behavior
-- Deploy this across all Windows endpoints managed by N-central

-- 1. Hunt for suspicious child processes of N-central components
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime,
       ParentPid, ParentName
FROM pslist()
WHERE (ParentName =~ '(?i)(java|dms|ncentral|agent)\.exe$'
   AND Name =~ '(?i)(cmd|powershell|wscript|rundll32|certutil)\.exe$')
   OR (Name =~ '(?i)agent\.exe$'
   AND CommandLine =~ '(?i)(whoami|net localgroup|sc config|reg add)')

-- 2. Check for recently modified N-central agent binaries (potential tampering)
LET agent_paths = "C:\\Program Files (x86)\\N-able Technologies\\Windows Agent\\bin\\**.exe"
SELECT FullPath, Size, Mtime, Ctime, hash(path=FullPath) as Hash
FROM glob(globs=agent_paths)
WHERE Mtime > now() - 86400 * 7  -- Modified in last 7 days
ORDER BY Mtime DESC

-- 3. Hunt for suspicious network connections from N-central server (if running on Windows)
SELECT Pid, Name, LocalAddr, LocalPort, RemoteAddr, RemotePort, State
FROM netstat()
WHERE Name =~ '(?i)(java|dms|ncentral)'
   AND RemotePort NOT IN (443, 80, 8443, 22)  -- Unexpected outbound ports
   AND RemoteAddr !~ '^(10\.|192\.168\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)'  -- External IPs
PowerShell
# N-central Emergency Patching and Verification Script
# Run this on your N-central server (Windows) to verify patch level and check for compromise indicators

# 1. Verify current N-central version and patch level
Write-Host "[+] Checking N-central Version..." -ForegroundColor Cyan
$ncentralPath = "C:\Program Files\N-able\N-central"
$versionFile = Join-Path $ncentralPath "version.txt"

if (Test-Path $versionFile) {
    $versionInfo = Get-Content $versionFile -Raw
    Write-Host "Current Version: $versionInfo" -ForegroundColor Yellow
    
    # Check if vulnerable version (2025.1 prior to HF4 or 2024.1 prior to HF8)
    if ($versionInfo -match "2025\.1" -and $versionInfo -notmatch "Hotfix 4|HF4") {
        Write-Host "[CRITICAL] Vulnerable version detected. Upgrade to 2025.1 HF4 immediately." -ForegroundColor Red
    }
    elseif ($versionInfo -match "2024\.1" -and $versionInfo -notmatch "Hotfix 8|HF8") {
        Write-Host "[CRITICAL] Vulnerable version detected. Upgrade to 2024.1 HF8 immediately." -ForegroundColor Red
    }
    else {
        Write-Host "[OK] Patched version detected." -ForegroundColor Green
    }
}
else {
    Write-Host "[WARNING] N-central installation not found at default path." -ForegroundColor Red
}

# 2. Check for suspicious processes spawned by N-central services
Write-Host "`n[+] Checking for suspicious process activity..." -ForegroundColor Cyan
$suspiciousProcesses = Get-WmiObject Win32_Process | Where-Object {
    ($_.ParentProcessId -ne 0) -and 
    ($_.Name -match "^(java|dms|ncentral)") -and 
    ($_.CommandLine -match "cmd|powershell|wscript|rundll32|certutil")
}

if ($suspiciousProcesses) {
    Write-Host "[ALERT] Suspicious processes detected:" -ForegroundColor Red
    $suspiciousProcesses | Select-Object ProcessId, Name, CommandLine, ParentProcessId | Format-Table -AutoSize
}
else {
    Write-Host "[OK] No suspicious child processes found." -ForegroundColor Green
}

# 3. Verify Legacy API is disabled (check listening ports and config)
Write-Host "`n[+] Checking Legacy API Status..." -ForegroundColor Cyan
$legacyPorts = @(80, 8080, 8443)  # Legacy SOAP API ports
$listening = Get-NetTCPConnection -State Listen | Where-Object { $_.LocalPort -in $legacyPorts }

foreach ($conn in $listening) {
    $proc = Get-Process -Id $conn.OwningProcess -ErrorAction SilentlyContinue
    if ($proc.ProcessName -match "java|dms") {
        Write-Host "[WARNING] Legacy API port $($conn.LocalPort) still active. Verify patch application." -ForegroundColor Red
    }
}

# 4. Check for unauthorized scheduled tasks or services (persistence)
Write-Host "`n[+] Checking for persistence mechanisms..." -ForegroundColor Cyan
$suspiciousTasks = Get-ScheduledTask | Where-Object {
    $_.TaskName -match "N-central|Nable|Update|Maintenance" -and
    $_.Principal.UserId -eq "SYSTEM" -and
    $_.Actions.Execute -match "powershell|cmd|wscript"
}

if ($suspiciousTasks) {
    Write-Host "[ALERT] Suspicious scheduled tasks found:" -ForegroundColor Red
    $suspiciousTasks | Select-Object TaskName, TaskPath, @{N='Command';E={$_.Actions.Execute}} | Format-List
}

# 5. Verify file integrity of critical N-central binaries
Write-Host "`n[+] Checking file integrity..." -ForegroundColor Cyan
$criticalFiles = @(
    "C:\Program Files\N-able\N-central\bin\dms.exe",
    "C:\Program Files\N-able\N-central\bin\java.exe",
    "C:\Program Files (x86)\N-able Technologies\Windows Agent\bin\agent.exe"
)

foreach ($file in $criticalFiles) {
    if (Test-Path $file) {
        $hash = Get-FileHash $file -Algorithm SHA256
        $lastWrite = (Get-Item $file).LastWriteTime
        Write-Host "File: $file" -ForegroundColor Gray
        Write-Host "  SHA256: $($hash.Hash)" -ForegroundColor Gray
        Write-Host "  Last Modified: $lastWrite" -ForegroundColor Gray
        
        # Alert if modified in last 7 days (potential tampering)
        if ($lastWrite -gt (Get-Date).AddDays(-7)) {
            Write-Host "  [WARNING] Recently modified - verify against deployment records" -ForegroundColor Yellow
        }
    }
}

Write-Host "`n[+] Assessment complete. If any alerts were generated, isolate the server and initiate incident response procedures." -ForegroundColor Cyan

Remediation

Immediate Actions (Next 24 Hours)

  1. Isolate N-central Servers: If your N-central instance is exposed to the internet (even behind a VPN or firewall), restrict access to trusted management IPs immediately. The authentication bypass flaws do not require valid credentials.

  2. Apply Emergency Patches:

    • N-central 2025.1: Upgrade to 2025.1 Hotfix 4 (build 2025.1.0.400 or later)
    • N-central 2024.1 LTS: Upgrade to 2024.1 Hotfix 8 (build 2024.1.0.800 or later)
    • N-central 2023.2: No patch available. You must migrate to a supported branch immediately. Treat any 2023.2 instance as compromised.
  3. Disable Legacy APIs (Pre-Patch Workaround): If you cannot patch immediately, block all traffic to /dms/services/* and /soap/* endpoints at the WAF or reverse proxy. N-able has permanently deprecated these endpoints; functionality will not be restored.

Post-Patching Verification (Next 72 Hours)

  1. Hunt for Persistence: Run the detection queries provided above. Look specifically for:

    • Unauthorized user accounts in the N-central console (Settings > Users)
    • Newly created scheduled tasks or services on the N-central server
    • Unusual script deployments in the N-central audit logs (especially PowerShell or batch scripts)
  2. Credential Rotation: Assume that any credentials stored in or accessible via N-central are compromised:

    • Rotate all domain administrator and local administrator passwords for managed endpoints
    • Revoke and reissue API tokens for integrated PSA tools (ConnectWise, Autotask, etc.)
    • Reset SNMP community strings and WMI credentials stored in N-central
  3. Review API Integrations: The legacy SOAP API is dead. Migrate any custom scripts or third-party integrations to the modern REST API (v2) using OAuth 2.0. The REST API enforces granular permissions and token expiration—features absent from the legacy implementation.

Long-Term Hardening

  1. Network Segmentation: Move N-central to a dedicated management VLAN. Do not allow inbound connections from managed customer networks to the N-central server—only outbound agent check-ins should be permitted.

  2. Enable MFA: Enforce multi-factor authentication for all N-central administrative accounts, including service accounts. The authentication bypass flaws targeted weak or absent MFA on the legacy API.

  3. Agent Hardening: Configure the N-central agent to run with least privilege (avoid SYSTEM where possible, though this may limit functionality). Enable agent tamper protection and configure alerts for agent service stops.

  4. Monitor for Downstream Compromise: If you are an MSP, notify your customers immediately. Attackers may have used N-central to deploy malware to customer endpoints before you patched. Hunt for unauthorized software deployments, new local admin accounts, and suspicious PowerShell execution across all managed endpoints.

Official Resources

  • N-able Security Advisory: https://www.n-able.com/security-advisories (Advisory ID: N-central-2026-001)
  • CISA KEV Catalog: Monitor for the addition of specific CVE identifiers as they are assigned
  • Vendor Patch Download: Available through the N-able Partner Portal (authentication required)

CISA Deadline: Federal civilian executive branch agencies must apply patches by April 11, 2026. All other organizations should treat this as a 72-hour emergency patch cycle given the active exploitation.

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.