Quick answers
- Is CVE-2026-86218 exploited in the wild?
- Yes. CVE-2026-86218 is known to be exploited in the wild, first recorded on 8 September 2026. Treat it as urgent.
- How severe is CVE-2026-86218?
- Critical severity, with a CVSS score of 9.8, published 6 September 2026.
- Which products and versions are affected?
- N-able N-central.
- Is there a fix for CVE-2026-86218?
- 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-86218 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86218?
- Check whether you run N-able N-central. 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
N-able N-central is vulnerable to a static code injection attack that allows pre-authentication remote code execution. The vulnerability exists in the application logic that processes user input without proper sanitization or validation, enabling an attacker to inject arbitrary code that is executed on the server. The attack vector is network-based and requires no authentication or user interaction. Successful exploitation grants an attacker the ability to execute arbitrary code with the privileges of the N-central application, potentially leading to complete compromise of the management platform and all connected systems. No patch information is currently available from the advisory, though the vulnerability has been documented as actively exploited in the wild as of the publication date.
Affected products
- N-able N-central
Timeline
- 2026-09-08: disclosed
- exploited: Actively exploited in the wild