N-able N-central Multi-CVE Takeover — September 2026 Refresh

CVE-2026-86218 pre-auth RCE · CVE-2026-86206/86207 auth bypass · downstream RMM persistence
Threat
N-able N-central multi-CVE takeover
Type
Actively exploited remote-management platform compromise
Severity
Critical
Version
v0.2 Draft · 2026-09-07
Author
cybersecurity analyst
Confidence
High core-behavior confidence; tenant unverified
STATIC REVIEW PASSED
01

Executive Summary

What changed: N-able and Huntress published a rapid sequence of new N-central disclosures on 5–6 September 2026. CVE-2026-86206 and CVE-2026-86207 can bypass authentication and grant full platform access; Huntress reproduced that chain after a fully patched production instance was compromised on 4 September. N-able then assigned CVE-2026-86218, a separate pre-authentication remote-code-execution flaw scored 10.0, and released build 2026.3.1.14. This makes the prior HuntPack's 2026.3.1.7 remediation line stale even though its endpoint hunts remain useful.

How the current chain works: The September authentication-bypass chain reaches N-central administrative capability without a normal login. Huntress observed account-name anomalies that append strings such as .invalid to familiar-looking addresses and reconnaissance against /remoteControlAction.do?method=getPierDetails with appliance identifiers. The independent CVE-2026-86218 flaw affects every N-central build before 2026.3.1.14 and allows pre-authentication code execution. Public reporting does not disclose a safe, complete request signature for that RCE, so this refresh does not invent one.

Why the existing endpoint detections stay: N-central is a trusted remote monitoring and management plane. Once it is controlled, an operator can use Take Control, jobs, scripts, and agents to reach downstream systems. The August incidents established durable endpoint evidence: Cloudflared service creation, cloudflared tunnel execution and egress, a masquerading svchost.exe under a user profile, discovery-utility bursts, and remote-support breadcrumbs. All nine prior CQL searches are preserved, rewrapped with the current canonical headers, and kept separate from the appliance-only September indicators.

Operational limit: Falcon endpoint events cannot prove exploitation on an unsensored N-central appliance. The .invalid account pattern, getPierDetails probes, administrative changes, and Take Control sessions require N-central, reverse-proxy, identity, and Windows event logs. The six historical IPs include shared VPN exits, and the three historical relay hostnames may age; they remain contextual hunts rather than automatic blocks. Every query is static-reviewed only: no tenant parse, positive fixture, benign baseline, schedule, IOA, prevention, or deployment is claimed.

Defender priority: Upgrade every self-hosted N-central server to 2026.3.1.14 or later, preserve appliance and proxy logs before changing access, audit new/renamed administrators and Take Control sessions, then run Q01–Q04 across every managed Windows endpoint through a channel independent of N-central.
PriorityWhy nowCoverage deliveredKey limitation
Find durable behavior and preserve evidenceCurrent and independently corroborated 2026 reporting9 CQL designs plus native pivotsStatic-only; tenant, content, and native-log semantics remain unverified
02

Source and Claim Review

Current-run sanitized plain-text snapshots were hashed before assembly. Every source was treated as untrusted data; no embedded instruction, command, exploit code, payload, or destination was executed.

IDPublisherTierIndependenceAccessedStatus
S01N-ableT1n-able2026-09-07T11:06:52Zsuccessful sanitized vendor/CVE extraction
S02N-able StatusT1n-able2026-09-07T11:06:52Zsuccessful sanitized vendor advisory extraction
S03HuntressT1huntress2026-09-07T11:06:52Zsuccessful sanitized first-hand incident and reproduction extraction
S04N-able and Huntress archived incident evidenceT1n-able-huntress-august2026-09-07T11:06:52Zarchived sanitized primary evidence revalidated for preservation
S05CISAT1cisa2026-09-07T11:06:52Zsuccessful sanitized government guidance extraction
ClaimStatementSourcesConfidence
C01The previous fixed build 2026.3.1.7 is superseded and no longer sufficient for the September disclosures.S01, S02, S03high
C02CVE-2026-86206 and CVE-2026-86207 can bypass N-central authentication controls and grant full platform access.S02, S03high
C03CVE-2026-86218 is a separate pre-authentication remote-code-execution flaw affecting N-central before 2026.3.1.14.S01, S03high
C04Huntress investigated a compromise of a then-current N-central deployment and reproduced the CVE-2026-86206/86207 chain, while noting the exact intrusion vector could not be proven from limited appliance history.S03high
C05Observed September pivots included account names with unexpected suffixes such as .invalid and probes to /remoteControlAction.do?method=getPierDetails.S03high
C06Earlier N-central exploitation used Take Control and produced downstream Cloudflared service and user-profile svchost.exe evidence.S03, S04high
C07The retained six IPs and three relay hostnames came from the prior incident evidence; two addresses were identified as commercial VPN exits and require corroboration.S04high
C08The N-central appliance often lacks endpoint sensor coverage, making central appliance and reverse-proxy log retention critical.S03high
C09No safe public request signature proves CVE-2026-86218 exploitation; the exploit itself remains an application-log and forensics gap.S01, S03high
C10Self-hosted operators must apply the current hotfix, restrict console access, audit platform users and sessions, and inspect downstream endpoints for post-access activity.S01, S02, S03high
Contradictions and gaps: infrastructure and public services are volatile; native log schemas and Falcon result semantics are tenant-specific; a hit does not prove every described capability or attribution.
03

Hunt Brief and Attack Chain

The scaffold separates queryable endpoint behaviors from application, content, memory, and forensics gaps. Each hypothesis retains evidence and a safe validation plan.

StepClaimsBehaviorPlatformGoal
1C03an unauthenticated actor reaches a vulnerable N-central serviceWindows and N-central appliancePreserve proxy and appliance access logs
2C02,C04,C05access controls are bypassed or code executes before authenticationWindows and N-central applianceFind unexpected users, .invalid suffixes, and getPierDetails probes
3C06the actor uses N-central administration or Take ControlWindows and N-central applianceReconcile sessions, jobs, scripts, and target devices
4C06downstream tools and persistence are delivered to managed endpointsWindows and N-central applianceFind Cloudflared service and masquerading svchost evidence
5C06,C07the actor establishes tunnel egress or contacts historical relaysWindows and N-central applianceCorrelate endpoint process, DNS, and network evidence
6C10defenders patch, preserve, scope, and recoverWindows and N-central applianceUpgrade to 2026.3.1.14+ and re-hunt independently
IDBehaviorTelemetryUseLookbackValidation
H01Cloudflared service, process, or tunnel egress appears on a managed endpointCreateService / ProcessRollup2 / NetworkConnectIP4alert-candidate30dUse an approved cloudflared fixture on an isolated test host, then baseline sanctioned connector hosts and paths.
H02A masquerading svchost.exe is written or runs from a user-profile pathPeFileWritten / NewExecutableWritten / ProcessRollup2alert-candidate30dUse a harmless renamed fixture in a lab path and confirm analysis-host exclusions do not suppress the path rule.
H03A managed endpoint communicates with a retained historical incident addressNetworkConnectIP4 / NetworkReceiveAcceptIP4hunt7dRun as a contextual pivot only and require another signal because two addresses are shared VPN exits.
H04A managed endpoint resolves a retained incident relay hostnameDnsRequest / SuspiciousDnsRequesthunt30dValidate resolver attribution and current ownership; do not contact the hostname during testing.
H05Discovery utilities cluster inside a suspect remote-support windowProcessRollup2 / SyntheticProcessRollup2hunt7dScope to a known Take Control window and baseline RMM inventory jobs before interpreting a cluster.
H06A new Windows service runs from a user-writable pathCreateServicehunt30dBaseline approved deployment agents and test with an inert disabled service in an isolated lab.
H07Unexpected or lookalike N-central administrative accounts appearN-central audit and identity logsgap30dExport platform users and audit history; compare names, creation times, roles, and source addresses to change records.
H08Pre-authentication requests probe or exploit the N-central servicereverse-proxy and N-central application logsgap30dPreserve raw requests and response metadata; use vendor or IR signatures only when a safe authoritative signature is published.

Affected surface and telemetry

N-central appliance logs plus Falcon process, file, DNS, service, and IPv4 network telemetry on managed Windows endpoints. Proxy, IPv6, resolver attribution, wrapper depth, memory, packet content, and product-native schema remain repository- and tenant-dependent.

04

Consolidated IOC Table

IDTypeValueSourceUse
I01ipv4173.249.252.200S04historical contextual hunt
I02ipv487.249.138.34S04shared VPN exit; corroborate
I03ipv437.19.210.32S04shared VPN exit; corroborate
I04ipv468.235.46.214S04historical contextual hunt
I05ipv437.153.90.88S04historical contextual hunt
I06ipv492.118.112.181S04historical contextual hunt
I07domainmousears.synology.meS04historical contextual hunt
I08domainwagoosh.direct.quickconnect.toS04historical contextual hunt
I09domainwho-ripped-one.direct.quickconnect.toS04historical contextual hunt

These retained values require current ownership and same-host corroboration before any block action.

05

ATT&CK Mapping

Every technique row is an analyst inference from source-backed behavior, not an unsupported actor attribution.

TacticTechniqueNameBehaviorBasisSources
Initial AccessT1190Exploit Public-Facing Applicationpre-authentication N-central accessanalyst inferenceS01,S02,S03
PersistenceT1136Create Accountunexpected administrative accountsanalyst inferenceS03
Command and ControlT1219Remote Access SoftwareN-central Take Control abuseanalyst inferenceS03,S04
PersistenceT1543.003Windows ServiceCloudflared or other user-path serviceanalyst inferenceS04
Defense EvasionT1036.005Match Legitimate Resource Name or Locationsvchost.exe under a user profileanalyst inferenceS04
Command and ControlT1572Protocol Tunnelingcloudflared tunnel process and egressanalyst inferenceS04
DiscoveryT1057Process Discoveryutility burst after remote accessanalyst inferenceS03,S04
06

Native / Non-CQL Hunts

HuntLog sourceLogicResponse
N-central user and role auditN-central platform audit/user exportFind accounts created or renamed near the incident window, especially familiar-looking names with unexpected suffixes such as .invalid; compare role grants and source addresses to approved changes.Disable only after preserving the record and obtaining platform-owner/incident authority.
getPierDetails reconnaissance reviewreverse proxy and N-central access logsSearch for /remoteControlAction.do?method=getPierDetails and retain source, appliance ID, response code, session, and adjacent requests without replaying them.Escalate when the request is unapproved or correlates with account/session anomalies.
Take Control session reconciliationN-central audit logs and Windows Event IDs 8192/8193Compare every session, script, job, and target device to an approved operator and ticket; retain endpoint support logs independently of N-central.Scope all downstream targets before restoring trust in the management plane.
Fixed-build and exposure inventoryN-central console plus perimeter inventoryConfirm every self-hosted instance reports build 2026.3.1.14 or later and is restricted to approved management paths.Patch before reconnecting; hosted NCOD status must be verified with the vendor.
07

CrowdStrike LogScale CQL Hunt Queries

Pick your tenant's cloud first — every "Open in Falcon" button below uses this selection.
Query strategy: Q01 and Q02 are the strongest keepers. Broader process, file, DNS, and network searches require owner and same-host correlation. Every card remains STATIC-ONLY.
Q01 · Cloudflared service registration on an N-central-managed endpoint
CONF highFP lowCOST low

Looks for: a Windows service whose display name or image path references cloudflared. Accomplishes: preserves the strongest service-persistence hunt from the prior pack and exposes tunnel installation on a downstream endpoint after RMM access.

Trace: H01 · A01

// HUNT: Cloudflared service registration on an N-central-managed endpoint
// HYPOTHESIS: H01
// USE: alert-candidate
// MITRE: T1543.003, T1572
// CONF: high
// FP: low
// COST: low
// TIMEFRAME: 30d — bounded analyst review window
// REQUIRES: CreateService; ServiceDisplayName, ServiceImagePath, ComputerName, UserName, aid
// FALSE POSITIVES: organizations that legitimately run Cloudflare Tunnel or Zero Trust connectors
// TUNING: exclude only owner-approved connector hosts by ComputerName after path and change review
// VALIDATION: STATIC-ONLY
#event_simpleName = /^CreateService$/
| ServiceDisplayName = /cloudflared/i or ServiceImagePath = /cloudflared/i
| table([@timestamp, aid, ComputerName, UserName, ServiceDisplayName, ServiceImagePath])
| sort(@timestamp, order=desc, limit=200)
Q02 · PE named svchost.exe written into a user profile directory
CONF highFP lowCOST low

Looks for: a PE named svchost.exe written beneath a user's Documents, Downloads, Desktop, or Public path. Accomplishes: retains the prior pack's high-fidelity masquerading-file signal before execution while preserving writer context.

Trace: H02 · A02

// HUNT: PE named svchost.exe written into a user profile directory
// HYPOTHESIS: H02
// USE: alert-candidate
// MITRE: T1036.005
// CONF: high
// FP: low
// COST: low
// TIMEFRAME: 30d — bounded analyst review window
// REQUIRES: PeFileWritten or NewExecutableWritten; TargetFileName, ContextBaseFileName, aid
// FALSE POSITIVES: malware-analysis or incident-response systems staging a known sample
// TUNING: exclude only named analysis hosts and exact case windows; do not widen the path rule
// VALIDATION: STATIC-ONLY
#event_simpleName = /^(PeFileWritten|NewExecutableWritten)$/
| TargetFileName = /\\Users\\[^\\]+\\(Documents|Downloads|Desktop|Public)\\/i
| TargetFileName = /\\svchost\.exe$/i
| table([@timestamp, aid, ComputerName, UserName, TargetFileName, ContextBaseFileName])
| sort(@timestamp, order=desc, limit=200)
Q03 · Masquerading svchost.exe running outside System32
CONF highFP lowCOST low

Looks for: svchost.exe executing from a user-writable profile path rather than a Windows system directory. Accomplishes: keeps the prior pack's execution-side confirmation and returns lineage, command line, and hash for incident scoping.

Trace: H02 · A03

// HUNT: Masquerading svchost.exe running outside System32
// HYPOTHESIS: H02
// USE: alert-candidate
// MITRE: T1036.005
// CONF: high
// FP: low
// COST: low
// TIMEFRAME: 30d — bounded analyst review window
// REQUIRES: ProcessRollup2 or SyntheticProcessRollup2; FileName, ImageFileName, CommandLine, SHA256HashData, aid
// FALSE POSITIVES: authorized malware-analysis systems
// TUNING: exclude only isolated research assets with case ownership and a bounded window
// VALIDATION: STATIC-ONLY
#event_simpleName = /^(ProcessRollup2|SyntheticProcessRollup2)$/
| FileName = /^svchost\.exe$/i
| ImageFileName = /\\Users\\[^\\]+\\(Documents|Downloads|Desktop|AppData|Public)\\/i
| table([@timestamp, aid, ComputerName, UserName, ImageFileName, CommandLine, ParentBaseFileName, SHA256HashData])
| sort(@timestamp, order=desc, limit=200)
Q04 · cloudflared execution or tunnel arguments on a managed endpoint
CONF highFP mediumCOST low

Looks for: cloudflared execution or command lines with tunnel run, token, or URL arguments. Accomplishes: retains the process-side tunnel hunt and identifies sanctioned-versus-unapproved connector context without relying on a listening port.

Trace: H01 · hunt-only

// HUNT: cloudflared execution or tunnel arguments on a managed endpoint
// HYPOTHESIS: H01
// USE: hunt
// MITRE: T1572, T1219
// CONF: high
// FP: medium
// COST: low
// TIMEFRAME: 30d — bounded analyst review window
// REQUIRES: ProcessRollup2 or SyntheticProcessRollup2; FileName, ImageFileName, CommandLine, ParentBaseFileName, aid
// FALSE POSITIVES: developer quick tunnels and sanctioned Cloudflare Zero Trust connectors
// TUNING: exclude approved connector hosts and signed paths; never exclude solely by attacker-controlled parent
// VALIDATION: STATIC-ONLY
#event_simpleName = /^(ProcessRollup2|SyntheticProcessRollup2)$/
| FileName = /^cloudflared(\.exe)?$/i or CommandLine = /\btunnel\s+(run|--token|--url)\b/i
| table([@timestamp, aid, ComputerName, UserName, FileName, ImageFileName, CommandLine, ParentBaseFileName, SHA256HashData])
| sort(@timestamp, order=desc, limit=300)
Q05 · Endpoint traffic to retained N-able incident addresses
CONF mediumFP highCOST medium

Looks for: IPv4 connections involving the six addresses retained from the prior incident pack. Accomplishes: preserves historical network pivots but keeps the two shared VPN exits in a same-host corroboration workflow.

Trace: H03 · hunt-only

// HUNT: Endpoint traffic to retained N-able incident addresses
// HYPOTHESIS: H03
// USE: hunt
// MITRE: T1071, T1090
// CONF: medium
// FP: high
// COST: medium
// TIMEFRAME: 7d — bounded analyst review window
// REQUIRES: NetworkConnectIP4 or NetworkReceiveAcceptIP4; RemoteAddressIP4, ContextBaseFileName, aid
// FALSE POSITIVES: commercial VPN use, shared hosting, research, and historical telemetry
// TUNING: require Q01-Q04 or unexplained platform activity before incident escalation
// VALIDATION: STATIC-ONLY
#event_simpleName = /^(NetworkConnectIP4|NetworkReceiveAcceptIP4)$/
| in(RemoteAddressIP4, values=["173.249.252.200", "87.249.138.34", "37.19.210.32", "68.235.46.214", "37.153.90.88", "92.118.112.181"])
| table([@timestamp, aid, ComputerName, UserName, LocalAddressIP4, RemoteAddressIP4, RemotePort, ContextBaseFileName])
| sort(@timestamp, order=desc, limit=300)
Q06 · DNS resolution of retained incident relay hostnames
CONF mediumFP mediumCOST low

Looks for: DNS requests to the three relay hostnames retained from the prior N-central incident. Accomplishes: preserves the historical domain sweep while forcing ownership, resolver, and same-host checks before escalation.

Trace: H04 · hunt-only

// HUNT: DNS resolution of retained incident relay hostnames
// HYPOTHESIS: H04
// USE: hunt
// MITRE: T1071.001
// CONF: medium
// FP: medium
// COST: low
// TIMEFRAME: 30d — bounded analyst review window
// REQUIRES: DnsRequest or SuspiciousDnsRequest; DomainName, ContextBaseFileName, aid
// FALSE POSITIVES: security research, reassigned hosts, or legitimate Synology QuickConnect use
// TUNING: scope to the exact hostnames and correlate with endpoint/RMM evidence
// VALIDATION: STATIC-ONLY
#event_simpleName = /^(DnsRequest|SuspiciousDnsRequest)$/
| DomainName = /(^|\.)(mousears\.synology\.me|wagoosh\.direct\.quickconnect\.to|who-ripped-one\.direct\.quickconnect\.to)$/i
| table([@timestamp, aid, ComputerName, UserName, DomainName, ContextBaseFileName])
| sort(@timestamp, order=desc, limit=300)
Q07 · Discovery-utility burst scoped to a suspect remote-support window
CONF lowFP highCOST medium

Looks for: clustered discovery utilities and process-enumeration commands on the same host and user. Accomplishes: retains the prior low-fidelity post-access pivot for use only inside a known anomalous Take Control window.

Trace: H05 · hunt-only

// HUNT: Discovery-utility burst scoped to a suspect remote-support window
// HYPOTHESIS: H05
// USE: hunt
// MITRE: T1057
// CONF: low
// FP: high
// COST: medium
// TIMEFRAME: 7d — bounded analyst review window
// REQUIRES: ProcessRollup2 or SyntheticProcessRollup2; FileName, CommandLine, ComputerName, UserName, aid
// FALSE POSITIVES: RMM inventory, monitoring, backup preflight, and help-desk scripts
// TUNING: set the suspect host/time window first and exclude documented service accounts
// VALIDATION: STATIC-ONLY
#event_simpleName = /^(ProcessRollup2|SyntheticProcessRollup2)$/
| FileName = /^(tasklist|qprocess|quser|whoami|systeminfo|nltest|hostname)\.exe$/i or CommandLine = /get-process\b|win32_process/i
| groupBy([aid, ComputerName, UserName], function=[count(as=Hits), collect(FileName), collect(CommandLine)], limit=200)
| sort(Hits, order=desc, limit=100)
| table([ComputerName, UserName, Hits, FileName, CommandLine])
Q08 · New service whose image path sits in a user-writable directory
CONF mediumFP mediumCOST low

Looks for: service creation whose binary path points into Users, ProgramData, Temp, AppData, or Public. Accomplishes: retains the broad persistence backstop for payloads that change names while keeping vendor updater baselining explicit.

Trace: H06 · hunt-only

// HUNT: New service whose image path sits in a user-writable directory
// HYPOTHESIS: H06
// USE: hunt
// MITRE: T1543.003
// CONF: medium
// FP: medium
// COST: low
// TIMEFRAME: 30d — bounded analyst review window
// REQUIRES: CreateService; ServiceDisplayName, ServiceImagePath, ComputerName, aid
// FALSE POSITIVES: per-user updaters and deployment agents that legitimately stage services
// TUNING: baseline named vendor services; keep Users, AppData, and Temp paths high priority
// VALIDATION: STATIC-ONLY
#event_simpleName = /^CreateService$/
| ServiceImagePath = /\\(Users|ProgramData|Temp|AppData|Public)\\/i
| table([@timestamp, aid, ComputerName, UserName, ServiceDisplayName, ServiceImagePath])
| sort(@timestamp, order=desc, limit=300)
Q09 · Network sessions initiated by a cloudflared process
CONF highFP mediumCOST medium

Looks for: IPv4 network sessions whose process context is cloudflared. Accomplishes: retains the tunnel-egress view and lets analysts compare destination, port, host ownership, and approved connector inventory.

Trace: H01 · hunt-only

// HUNT: Network sessions initiated by a cloudflared process
// HYPOTHESIS: H01
// USE: hunt
// MITRE: T1572, T1102
// CONF: high
// FP: medium
// COST: medium
// TIMEFRAME: 7d — bounded analyst review window
// REQUIRES: NetworkConnectIP4; ContextBaseFileName, RemoteAddressIP4, RemotePort, aid
// FALSE POSITIVES: approved Cloudflare Zero Trust connectors
// TUNING: exclude only owner-approved connector hosts and compare with Q01/Q04
// VALIDATION: STATIC-ONLY
#event_simpleName = /^NetworkConnectIP4$/
| ContextBaseFileName = /^cloudflared(\.exe)?$/i
| groupBy([aid, ComputerName, ContextBaseFileName, RemoteAddressIP4, RemotePort], function=count(as=Hits), limit=500)
| sort(Hits, order=desc, limit=200)
| table([ComputerName, ContextBaseFileName, RemoteAddressIP4, RemotePort, Hits])
08

Operationalization and IOA Candidates

Every query has an explicit operational decision. Alert-candidate rows have complete design-only packages; no schedule, notification, IOA, or prevention rule was created.

QueryUseDecisionReadinessRationale
Q01alert-candidatealert-packagedesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Q02alert-candidatealert-packagedesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Q03alert-candidatealert-packagedesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Q04hunthunt-onlydesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Q05hunthunt-onlydesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Q06hunthunt-onlydesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Q07hunthunt-onlydesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Q08hunthunt-onlydesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Q09hunthunt-onlydesign-onlyTenant parsing, positive testing, and benign baseline are not recorded.
Readiness gate: every observed baseline is unknown and every positive/benign test is planned-not-run. No alert package is deployable.
09

Machine-Readable IOC Appendix

Values are retained from source-backed prior incident evidence and expire for mandatory review on 2026-12-07. Expiration is not evidence of safety.

Source-tagged CSV9 values
type,value,action,severity,expiration,description,tags
ipv4,173.249.252.200,detect,medium,2026-12-07,historical contextual hunt,source:S04
ipv4,87.249.138.34,detect,medium,2026-12-07,shared VPN exit; corroborate,source:S04
ipv4,37.19.210.32,detect,medium,2026-12-07,shared VPN exit; corroborate,source:S04
ipv4,68.235.46.214,detect,medium,2026-12-07,historical contextual hunt,source:S04
ipv4,37.153.90.88,detect,medium,2026-12-07,historical contextual hunt,source:S04
ipv4,92.118.112.181,detect,medium,2026-12-07,historical contextual hunt,source:S04
domain,mousears.synology.me,detect,medium,2026-12-07,historical contextual hunt,source:S04
domain,wagoosh.direct.quickconnect.to,detect,medium,2026-12-07,historical contextual hunt,source:S04
domain,who-ripped-one.direct.quickconnect.to,detect,medium,2026-12-07,historical contextual hunt,source:S04
Values onlyhunt input
173.249.252.200
87.249.138.34
37.19.210.32
68.235.46.214
37.153.90.88
92.118.112.181
mousears.synology.me
wagoosh.direct.quickconnect.to
who-ripped-one.direct.quickconnect.to
Handling notereview required
Source provenance proves transcription, not current ownership, maliciousness, or safe blocking. Require same-host corroboration.
10

Hardening — Tiered and Deployable

Immediate — expose and interrupt the active chain
  • Upgrade self-hosted N-central to 2026.3.1.14 or later (M1051; CTRL01) — preserve current build and audit evidence, take the approved backup, then apply HF4 through the vendor-supported path deployable-design Verify: confirm the build is at least 2026.3.1.14 and core management functions pass owner health checks Rollback: restore only through the vendor-supported rollback/recovery path; keep network exposure restricted Authority: N-able CVE-2026-86218 advisory dated 2026-09-06.
  • Restrict N-central console access while compromise assessment runs (M1030; CTRL02) — allow only reviewed management sources through a tested access-control layer and keep an emergency owner-approved path deployable-design Verify: confirm approved administration succeeds and an unapproved test source is denied and logged Rollback: restore the exported rule set for the pilot path if management continuity fails Authority: N-able and Huntress guidance accessed 2026-09-07.
  • Audit administrators, roles, API access, scripts, and Take Control sessions (M1047; CTRL03) — export current state and reconcile every recent high-privilege change and downstream action to an owner and ticket deployable-design Verify: unexplained .invalid or lookalike accounts and sessions are preserved and escalated Rollback: reverse only analyst-approved unauthorized changes after evidence capture Authority: Huntress incident guidance accessed 2026-09-07.
Near-term — constrain repeat execution and egress
  • Sweep downstream endpoints through an independent channel (M1040; CTRL04) — run the preserved Q01-Q09 hunts outside N-central and acquire suspicious service, process, file, DNS, and network evidence deployable-design Verify: every N-central-managed endpoint is reconciled to sensor coverage and unexplained hits enter incident handling Rollback: the sweep is read-only; remove temporary collection tooling and retain results Authority: N-able and Huntress August/September incident evidence.
  • Constrain RMM-launched scripts and tunnel clients (M1038; CTRL05) — pilot application and egress controls for unapproved tunnel clients, user-path services, and RMM-launched tools deployable-design Verify: approved support workflows pass while an inert unapproved fixture is detected or blocked Rollback: restore the exported pilot policy and retain alert-only monitoring Authority: CISA risk-prioritized remediation guidance and N-able incident evidence.
Strategic — retire unowned trust paths
  • Separate management-plane trust and retain logs off appliance (M1047; CTRL06) — forward N-central, proxy, identity, Take Control, job, and downstream agent logs to a separately administered repository with tested retention deployable-design Verify: simulate an appliance outage and confirm the central record preserves users, sessions, requests, and target actions Rollback: restore prior forwarding only if the replacement retains equivalent independent evidence Authority: CISA BOD 26-04 implementation guidance.

Deployable playbook · PB01 · guarded pilot and rollback

  1. Confirm change authority and preserve build, users, roles, proxy, audit, Take Control, script, and job records
  2. restrict console exposure without cutting off the emergency management path
  3. back up and upgrade a non-production or lowest-risk instance to 2026.3.1.14
  4. verify build and platform health
  5. expand under change control
  6. independently sweep downstream endpoints with Q01-Q09
  7. rollback only through vendor-supported recovery or the exported access policy
  8. retain evidence, owner decisions, and the post-upgrade re-hunt
Design state: no control was canary-tested or deployed. Complete platform, continuity, sensitive-data, and approval checks first.
11

Containment Runbook

PhaseTriggerAuthorityOwnerEvidenceRecovery
1. Preserve and validatesuspected account, request, session, or endpoint hitSOC leadSOC analyst and N-central ownerraw platform/proxy records, build, users, roles, jobs, scripts, sessionsnone; evidence capture is read-only
2. Restrict management-plane accesscredible unauthorized access or exposed unpatched serverincident commander plus service ownernetwork and platform operationsrule export, allowed emergency path, denied-source testrestore prior reviewed access policy if continuity stop condition fires
3. Scope downstream actionsunexplained administrator or Take Control activityincident commanderSOC and endpoint responsetarget devices, support logs, process trees, services, files, DNS/networkdocument legitimate action or continue containment
4. Contain compromised systemsdownstream persistence or execution corroboratedincident commander plus business ownerendpoint operationsisolation time, exceptions, credentials/tokens affectedtemporary access only under continuity plan
5. Patch, recover, and re-huntevidence preserved and scope stableincident commander and N-central ownerplatform, endpoint, and SOC teamsbuild 2026.3.1.14+, health checks, fresh Q01-Q09 and native resultsrestore service after no unexplained findings and owner approval

Preservation order: raw results, application/proxy events, process tree, files and hashes, network/DNS, identity/session state, policy/configuration, analyst notes, and tool logs. Closure: known-good recovery, explained re-hunt results, and incident-commander plus system-owner approval.

12

Detection Coverage and Validation Evidence

Validation state: STATIC REVIEW PASSED only after the complete local gate suite succeeds. This is not Falcon parsing, canary success, schedule creation, or deployment evidence.

TechniqueCoverageQuery or handoffEvidenceLimitation
T1190Static or gapnative/memory handofflocal structure, field, syntax, provenance, and safety reviewtenant parser, positive test, and benign baseline absent
T1136Static or gapnative/memory handofflocal structure, field, syntax, provenance, and safety reviewtenant parser, positive test, and benign baseline absent
T1219Static or gapQ04local structure, field, syntax, provenance, and safety reviewtenant parser, positive test, and benign baseline absent
T1543.003Static or gapQ01, Q08local structure, field, syntax, provenance, and safety reviewtenant parser, positive test, and benign baseline absent
T1036.005Static or gapQ02, Q03local structure, field, syntax, provenance, and safety reviewtenant parser, positive test, and benign baseline absent
T1572Static or gapQ01, Q04, Q09local structure, field, syntax, provenance, and safety reviewtenant parser, positive test, and benign baseline absent
T1057Static or gapQ07local structure, field, syntax, provenance, and safety reviewtenant parser, positive test, and benign baseline absent

Recorded evidence and next tests

  • Every CQL card retains VALIDATION: STATIC-ONLY; no Falcon tenant was contacted.
  • The offline tenant dry run checks extraction and profile readiness only.
  • Content, memory, product-native, IPv6, proxy, and wrapper-depth gaps remain visible.
  • Next: parse Q01 and Q02 in the intended repository over one hour, verify fields, then run approved inert positive and 30-day benign tests.
13

Hunt Summary Ticket

TITLE:        N-able N-central multi-CVE takeover hunt — v0.2 Draft
SEVERITY:     critical — current evidence supports high-impact compromise and downstream control risk
SCOPE:        N-central appliance logs plus Falcon process, file, DNS, service, and IPv4 network telemetry on managed Windows endpoints
HYPOTHESIS:   H01 alert-candidate — Cloudflared service, process, or tunnel egress appears on a managed endpoint; H02 alert-candidate — A masquerading svchost.exe is written or runs from a user-profile path; H03 hunt — A managed endpoint communicates with a retained historical incident address; H04 hunt — A managed endpoint resolves a retained incident relay hostname; H05 hunt — Discovery utilities cluster inside a suspect remote-support window; H06 hunt — A new Windows service runs from a user-writable path; H07 gap — Unexpected or lookalike N-central administrative accounts appear; H08 gap — Pre-authentication requests probe or exploit the N-central service
QUERIES RUN:  Q01 alert-candidate; Q02 alert-candidate; Q03 alert-candidate; Q04 hunt; Q05 hunt; Q06 hunt; Q07 hunt; Q08 hunt; Q09 hunt
DO FIRST:     Q01 and Q02 over 30d
FINDINGS:
GAPS:         tenant parsing, native/content/memory evidence, positive and benign tests
ACTIONS:      SOC validates Q01/Q02; platform and endpoint owners preserve and scope evidence
OWNER:        Security Operations / Detection Engineering / Platform Owner
VERSION:      v0.2 Draft · 2026-09-07 · STATIC REVIEW PASSED
14

Changelog

v0.2 Draft2026-09-07Preservative refresh for CVE-2026-86206, CVE-2026-86207, and CVE-2026-86218; fixed build advanced to 2026.3.1.14. All nine prior queries and nine prior atomic pivots were retained, canonicalized, and re-gated; new appliance-log pivots were added without inventing an RCE signature.
v0.12026-08-03Initial N-central CVE-2026-18556/18577 report with nine endpoint CQL hunts, retained contextual infrastructure, hardening, and response guidance.
15

References

IDPublisherVersion/statusAccessedUseURL
S01N-ablesuccessful sanitized vendor/CVE extraction2026-09-07T11:06:52ZC01, C03, C09, C10https://me.n-able.com/s/security-advisory/aArVy0000002Ld3KAE/cve202686218-preauthentication-remote-code-execution
S02N-able Statussuccessful sanitized vendor advisory extraction2026-09-07T11:06:52ZC01, C02, C10https://status.n-able.com/2026/09/05/n-central-2026-3-hotfix-3-cve-2026-86206-and-cve-2026-86207/
S03Huntresssuccessful sanitized first-hand incident and reproduction extraction2026-09-07T11:06:52ZC01, C02, C03, C04, C05, C06, C08, C09, C10https://www.huntress.com/blog/n-able-vulnerability-exploitation
S04N-able and Huntress archived incident evidencearchived sanitized primary evidence revalidated for preservation2026-09-07T11:06:52ZC06, C07https://status.n-able.com/2026/08/02/n-central-2026-3-hotfix-1-mitigation-for-cve-2026-18577/
S05CISAsuccessful sanitized government guidance extraction2026-09-07T11:06:52ZC10https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk