CVE-2026-86207: N-able N-central authentication bypass in internal APIs

CVE-2026-86207 · Severity: info · Published 2026-09-05

N-central is a remote management platform used by IT service providers to manage customer networks and infrastructure. This authentication bypass vulnerability in internal APIs allows an attacker to gain unauthorized access to the entire N-central platform without valid credentials, potentially compromising management of all monitored customer systems and exposing sensitive infrastructure data.

Technologies: N-able N-central. Vendors: N-able.

Quick answers

Is CVE-2026-86207 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-86207 being exploited in the wild.
How severe is CVE-2026-86207?
Informational severity, published 5 September 2026.
Which products and versions are affected?
N-able N-central before 2026.3 HF3 (2026.3.1.13).
Is there a fix for CVE-2026-86207?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-86207 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-86207?
Check whether you run N-able N-central at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This vulnerability is an authentication bypass affecting internal-only APIs in N-central versions prior to 2026.3 HF3. The root cause and attack vector are not fully detailed in available sources, but the advisory indicates that an attacker can bypass authentication controls to gain unauthorized access to the platform. The vulnerability is remotely exploitable and affects both on-premises and hosted deployments (though hosted instances were patched before public disclosure). The fix is available in N-central 2026.3 HF3 (build 2026.3.1.13) and later; customers must upgrade on-premises instances immediately. No public exploitation has been confirmed.

Affected products

  • N-able N-central before 2026.3 HF3 (2026.3.1.13)

Timeline

  • 2026-09-05: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.