PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-86218 – Pre-Authentication Remote Code Execution – N-able N-central (before 2026.3.1.14)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86218 is a critical, pre-authentication remote code execution vulnerability in N-able N-central, an on-premises remote monitoring and management (RMM) platform used by managed service providers. The flaw is classified as CWE-96 (Improper Neutralization of Directives in Statically Saved Code / "static code injection") and can be exploited by a remote, unauthenticated attacker with no user interaction required. It carries a maximum CVSS score of 10.0 and affects all N-central versions prior to 2026.3.1.14.

Technical details

  • Root cause: Improper neutralization of directives in statically saved code (CWE-96), allowing attacker-supplied input to be injected into and later executed as code on the server.
  • Trigger conditions: No authentication, privileges, or user interaction are required to exploit the flaw.
  • Attack vector: Network — the vulnerable component is reachable directly over the network without any prerequisite access.
  • Impact: Successful exploitation results in remote code execution, with high impact to confidentiality, integrity, and availability of the affected system and, per the published metrics, subsequent systems it manages.

Affected software

  • N-able N-central — all versions prior to 2026.3.1.14

Severity

  • CVSS v4.0 Base Score: 10.0 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Mitigation and recommended actions

  • Immediate: Upgrade N-central to version 2026.3.1.14 or later, where the vulnerability is fixed.
  • If immediate patching is not possible: Restrict network exposure of the N-central management interface (e.g., place it behind a VPN or firewall allow-list limiting access to trusted management networks) until the upgrade can be applied, and monitor N-central server logs for anomalous activity given this platform’s recent history of active exploitation.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: N-central Login Redirect

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge