N-able N-central's Able2Shell zero-days got a hotfix, and the researcher says new chains beat it; here's how to protect your clients' servers.
An MSP's N-central server runs commands on the client machines it manages, so a public exploit for it could hand an attacker far more than one box. On 11 November 2026, the researcher behind the "Able2Shell" N-central zero-day dump released two new chains they say beat N-able's day-old hotfix, Huntress reports. Check every client's N-central server today, patched or not.
Able2Shell is researcher Sean Bales's name for 33 flaws, by the researcher's count, in N-able N-central, the remote monitoring and management (RMM) console MSPs use to run client machines, among them path traversal bug CVE-2026-125882. Huntress says three of its four chains give unauthenticated remote code execution and one gives root, the server's top account. N-able saw scanning but no successful customer exploitation, as quoted by Huntress; Previdian's decoy server logged 68 probe and exploit-attempt events from one IP from about 22:00 UTC on 9 November 2026. CVE-2026-125882 is rated 8.6 (CVSS) and needs a high-privilege login. CISA has not listed it as of this writing; recheck the catalog.
The researcher tested N-central Appliance 2026.4.0.31, and Huntress says earlier versions are likely affected. N-able's HF2, build 2026.4.1.26, shipped on 10 November 2026 and fixes seven CVEs:
| CVE | Weakness (per N-able) | Fixed in |
|---|---|---|
| CVE-2026-125878 | OGNL injection (code smuggled into a template language) | 2026.4.1.26 |
| CVE-2026-125879 | Local privilege escalation to root via a syslog-ng config | 2026.4.1.26 |
| CVE-2026-125880 | Stored cross-site scripting via patch metadata | 2026.4.1.26 |
| CVE-2026-125881 | Server-side request forgery via service import | 2026.4.1.26 |
| CVE-2026-125882 | Remote code execution via file upload path traversal | 2026.4.1.26 |
| CVE-2026-125883 | XML external entity (XXE) flaws | 2026.4.1.26 |
| CVE-2026-91000 | Insecure IPC channels, local privilege escalation | 2026.4.1.26 |
Fixed builds from N-able's HF2 release notes. The 4EverAble2Shell write-up says it was verified against 2026.4.1.26 with the Legacy API turned on, and Huntress reported no fix for the new chains as of 12 November 2026.
Look back to 8 November 2026, when Censys dates the disclosure. Checks 1–3 and 5 use the console or your workstation; check 4 needs a root shell on an on-premises appliance (hosted: ask N-able support to run it, quoting the seven HF2 CVE ids); check 6 runs on managed Windows endpoints.
Preserve evidence. Download server logs from Administration Utilities > View Logs (N-able) and export Administration > User Management > Users to CSV (N-able), then hash the copies. Pass: $D.sha256 lists every file.
D=~/ir/ncentral-<client>-$(date +%F); mkdir -p "$D"
cp -a ~/Downloads/<n-central-log-and-user-files> "$D"/
sudo find "$D" -type f -exec sha256sum {} + | sudo tee "$D.sha256"
Confirm the build and the exposure. Read Help > Version Information, then request the console from outside the client network, matching Censys's "N-central" page title. Pass: the first command prints 000 and the second prints nothing; build 2026.4.1.26 alone is not a pass.
# checks the default page on 443/80 only; use the client's asset inventory as the primary list
curl -sk -m 10 -o /dev/null -w '%{http_code}\n' https://<n-central-host>/
curl -sk -m 10 http://<n-central-host>/ | grep -io '<title>[^<]*N-central'
Search logs for published indicators. Previdian's attacker IP, port and payload files, plus a request marker from Huntress's static analysis. A hit means contact with known attacker infrastructure: treat it as a likely compromise and escalate. Pass: no output.
grep -rniE '5\.231\.45\.175|:8097|/a\.dtd|/svc\.xml' "$D" <firewall-or-proxy-export>
# request bodies are often not logged, so a clean result here is weak
grep -rn 'jline.internal.TerminalLineSettings' "$D"
Look for Huntress's file indicators. On the appliance, list a flag-file symlink, serverchild temp files and task-output ZIPs containing CodeDropMeta.xml. Pass: all three commands print nothing.
sudo find /var/opt/n-central/flag -name flag_default.json -type l -ls
sudo find /var/opt/n-central/tmp -name 'serverchild-*' -ls
sudo find / -xdev -path '*scheduled_tasks/output_files/*.zip' -exec unzip -l {} \; | awk '/^Archive:/{a=$2} /CodeDropMeta\.xml/{print a}'
Review accounts, scripts and remote sessions. Read the user CSV for unknown admins, then search the client's syslog archive for N-central audit events. Pass: every account and hit matches work the MSP's staff did.
# only covers the time Audit Export was already switched on
zgrep -hE 'User Created|User Role Assign|User Script|Scheduled Task|System shell command|Remote (control|background) session' <syslog-archive>/*
Check managed Windows endpoints. Huntress flags SYSTEM PowerShell with -EncodedCommand launched by the N-able Agent, and CodeDrop folders near the Windows Software Probe. The process check sees running processes only. Pass: both checks print nothing.
$hosts = (Get-ADComputer -Filter 'Enabled -eq $true').Name
Invoke-Command -ComputerName $hosts -ErrorAction SilentlyContinue -ErrorVariable failed -ScriptBlock {
Get-CimInstance Win32_Process -Filter "Name='powershell.exe'" |
Where-Object CommandLine -match 'NoProfile -NonInteractive -EncodedCommand' |
Select-Object ProcessId, ParentProcessId, CommandLine
Get-CimInstance Win32_LogicalDisk -Filter 'DriveType=3' | ForEach-Object {
Get-ChildItem "$($_.DeviceID)\" -Recurse -Force -Directory -ErrorAction SilentlyContinue |
Where-Object FullName -match '\\CodeDrop(Tmp|\\ServiceBackup)$' | Select-Object FullName, LastWriteTime
}
}
$failed | ForEach-Object TargetObject # hosts that could not be checked
Huntress reports no fix yet for the new chains, so cut access first and treat HF2 as necessary, not sufficient.
Preserve evidence before anything changes. Confirm the evidence copies still match their hashes. Pass: every line reads OK.
sudo sha256sum -c "$D.sha256"
Close the door. Take each on-premises server offline or remove its internet access, even with HF2, as Huntress advises; an IP allowlist alone fails. Remote Agents stop checking in meanwhile. Pass: check 2's first command prints 000.
Install HF2. Upgrade the server to 2026.4.1.26, then Agents, then Probes, per N-able's release notes. Pass: Help > Version Information shows 2026.4.1.26.
Remove footholds. Disable unknown users (per N-able), rebuild endpoints with check 6 hits, and lock unknown appliance logins with sudo usermod -L <user>. Pass: a fresh user CSV and this command show only recognised accounts.
sudo awk -F: '$7 !~ /(nologin|false)$/ {print $1}' /etc/passwd
Rotate credentials. With the server off the internet, reset remaining N-central passwords and client credentials stored in it. Pass: a login with an old password fails.
Hardening (agree with the client first). Turn on Administration > Audit Export with TLS on port 6514 (N-able). Pass: the Test Export record reaches the client's syslog server.
Rerun checks 2 to 6. Pass: check 2 prints 000 and checks 3, 4 and 6 print nothing.
HF2 fixed seven CVEs, but Huntress describes 4EverAble2Shell as a no-login chain to root on the server and Agent2Shell as more than ten flaws in how the server talks to Windows Agents and Probes. That second set is the MSP RMM worst case: by the researcher's claims, reaching the server is enough to run commands on managed endpoints.
It is also N-central's third zero-day episode since August, per Huntress: CVE-2026-18556 in August, CVE-2026-86218 in September, and now Able2Shell. Remote-access tools keep drawing this attention, as with the BeyondTrust remote support zero-day spies exploited and the ConnectWise backup app that let attackers skip the password.
KinoSec's autonomous web app pentest checks whether each client's N-central console answers from the internet and what an outsider can reach on it. With autonomous web app and API pentesting for your clients, KinoSec runs reconnaissance, finds vulnerabilities, chains them, and writes findings with remediation you can hand the client. Run it after you cut access and again after HF2: a hotfix is N-able's statement about its code, while an outside-in test shows whether that client's door is shut. KinoSec is built to test for this class of flaw; it does not read N-central logs or endpoints, so checks 3 to 6 stay with your team.
No. Able2Shell is the set of 33 flaws, by the researcher's count, published on 9 November 2026, and HF2 fixed seven CVEs from it. Huntress describes Agent2Shell as more than ten separate issues in how the N-central server talks to Windows Agents and Probes, which the researcher says work against HF2. Huntress reported no fix for it as of 12 November 2026.
Search the downloaded N-central logs for Previdian's indicators with grep -rniE '5\.231\.45\.175|/a\.dtd' "$D". On an on-premises appliance, run sudo find /var/opt/n-central/flag -type l -ls; a flag_default.json symlink is one of Huntress's indicators. On managed Windows endpoints, look for encoded PowerShell with gcim Win32_Process -Filter "Name='powershell.exe'".
Huntress says to take the server offline or remove all internet access to it, even with HF2 applied. It warns that an IP allowlist alone is not enough, because the affected endpoints are the ones Agents and Probes use to check in. Plan for remote endpoints to stop checking in until access returns, and confirm from outside with curl that the console gets no response.
Ask whether the console is reachable from the internet, when the MSP applied N-central HF2, and whether audit events leave the server through N-able's Audit Export to a syslog server. Ask, too, for an outside-in test of that console after each hotfix, not only the version number.