Quick answers
- Is CVE-2026-18556 exploited in the wild?
- Yes. CVE-2026-18556 is known to be exploited in the wild, first recorded on 4 August 2026. Treat it as urgent.
- How severe is CVE-2026-18556?
- Critical severity, with a CVSS score of 7.4, published 1 August 2026.
- Which products and versions are affected?
- N-able N-central through 2026.1.
- Is there a fix for CVE-2026-18556?
- A patch was published on 2026-08-02: N-able security update blog post published Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18556 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-18556?
- 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
An authentication bypass vulnerability (CWE-288) exists in N-able N-central through version 2026.1. The flaw involves the use of an alternate path or channel that allows an attacker to circumvent established authentication mechanisms. The attack vector is network-based and requires no prior privileges or user interaction, though it is rated with high attack complexity. Successful exploitation allows an attacker to bypass authentication entirely, potentially leading to full compromise of the N-central instance. N-able has released security updates to address this issue.
Affected products
- N-able N-central through 2026.1
Timeline
- 2026-08-01: disclosed: Initial N-able disclosure and NVD publication
- 2026-08-02: patched: N-able security update blog post published
- 2026-08-04: advisory: NVD assessment and CISA-ADP enrichment updated