How severe is CVE-2026-86218?

No CVSS score has been assigned to CVE-2026-86218 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-86218?

Affected package information for CVE-2026-86218 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-86218?

No fixed release is recorded for CVE-2026-86218 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2026-86218 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2026-86218 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-86218 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-86218 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-86218?

CVE-2026-86218 has an EPSS (Exploit Prediction Scoring System) score of 12.9%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2026-86218 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-86218 (N-able N-central Static Code Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-09-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-09-11. The required action was: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-86218?

CVE-2026-86218 is classified as CWE-96 (CWE-96). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2026-86218?

A Nuclei detection template exists for CVE-2026-86218, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-86218 published, and has it been updated?

CVE-2026-86218 was published on September 6, 2026 and was last updated on September 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2026-86218

CVE-2026-86218 is a CWE-96 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-09-08) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.

Published

Sep 6, 2026

Updated

Sep 9, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 6, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-09-08. Federal agencies were required to remediate by 2026-09-11.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-86218.

EPSS Exploitation Probability

via FIRST.org ↗

12.9%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.

Affected Products

1 product · 5 configurations

Application

n-centraln-able

< 2026.3

1 version

2026.3

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-86218 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2026-86218

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-86218 -u https://target

Template: N-able N-central <2026.3.1.14 - Pre-Authentication Remote Code Execution
Severity: critical
Impact: A successful exploit grants an unauthenticated attacker remote code execution on the N-central server with the service account's privileges, enabling full control of the N-central RMM platform and all managed endpoints, lateral movement to all customer networks managed by the MSP, credential harvesting from N-central's credential vault, and deployment of ransomware or backdoors across all managed infrastructure.
Remediation: Upgrade N-central immediately to version 2026.3.1.14 (Hotfix 4) or later. Direct upgrade paths exist from builds 2025.4, 2026.1, 2026.2, 2026.3, and all 2026.3.1 hotfixes. Additionally restrict inbound access to N-central with IP allowlisting or VPN, audit N-central user accounts for unauthorized accounts (especially .invalid emails), and review appliance logs for evidence of pre-exploitation reconnaissance.

Template by ProjectDiscovery nuclei-templates (DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.

O3 Security · Impact-Aware SCA

Is CVE-2026-86218 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2026-86218

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2026-86218

Frequently Asked Questions

Is CVE-2026-86218 in your dependencies?