Skip to content
major vulnerability· requires attention

Pre-auth RCE in widely used RMM (N-able N-central) enables mass compromise of managed customers and infrastructure.

Applications

CVE-2026-86218

10.0
Critical
KEV · Exploited in wildEPSS 0.74%Patch availableSep 7, 2026

Pre-auth remote code execution in N-able N-central (pre-2026.3.1.14), CVSS 10.0

common questions

Is CVE-2026-86218 being exploited?

Yes. CVE-2026-86218 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-86218?

CVE-2026-86218 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-86218?

Yes. A fix has been recorded for CVE-2026-86218. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-86218 affect?

CVE-2026-86218 affects N-able N-central < 2026.3.1.14, Managed endpoints via compromised N-central. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-86218?

Upgrade to 2026.3.1.14+, restrict access, rotate credentials, monitor logs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
N-able N-central < 2026.3.1.14Managed endpoints via compromised N-central
impact

Unauthenticated RCE on N-central server allowing full server takeover, malware deployment, and compromise of managed endpoints.

action required

Immediate action required

affected versions
N-able N-central
  • affected< 2026.3.1.14

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free