Quick answers
- Is CVE-2026-86206 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86206 being exploited in the wild.
- How severe is CVE-2026-86206?
- Informational severity, with a CVSS score of 8.6, published 5 September 2026.
- Which products and versions are affected?
- N-able N-central Before 2026.3 HF3 and 2026.4.
- Is there a fix for CVE-2026-86206?
- A patch was published on 2026-09-05: Fixed in N-central 2026.3 HF3 (2026.3.1.13) and 2026.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86206 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-86206?
- 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
A vulnerability in N-central's internal API access control filter fails to properly validate requests, allowing attackers to bypass authentication mechanisms and access internal APIs without valid credentials. The attack is network-accessible and requires no prior authentication or user interaction. An attacker exploiting this flaw can gain unauthorized access to sensitive internal APIs and potentially achieve full control of the N-central platform. The vulnerability is fixed in N-central 2026.3 HF3 (build 2026.3.1.13) and 2026.4. Hosted N-central instances (NCOD) have already been patched; on-premises deployments must upgrade immediately.
Affected products
- N-able N-central Before 2026.3 HF3 and 2026.4
Timeline
- 2026-09-05: disclosed: Published on NVD
- 2026-09-05: patched: Fixed in N-central 2026.3 HF3 (2026.3.1.13) and 2026.4