Quick answers
- Is CVE-2026-18577 exploited in the wild?
- Yes. CVE-2026-18577 is known to be exploited in the wild, first recorded on 3 August 2026. Treat it as urgent.
- How severe is CVE-2026-18577?
- Critical severity, with a CVSS score of 8.1, published 2 August 2026.
- Which products and versions are affected?
- N-able N-central through 2026.3.1.
- Is there a fix for CVE-2026-18577?
- A patch was published on 2026-08-02: N-central 2026.3 Hotfix 1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18577 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-18577?
- 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
N-able N-central is vulnerable to an authentication bypass using an alternate path or channel (CWE-288). This issue stems from an incomplete patch for CVE-2026-18556. A remote, unauthenticated attacker can exploit this flaw to bypass authentication mechanisms and achieve full account takeover. The vulnerability affects N-central versions through 2026.3.1. N-able has released N-central 2026.3 Hotfix 1 (version 2026.3.1.7) to address this issue. The vulnerability has reportedly been exploited in the wild.
Affected products
- N-able N-central through 2026.3.1
Timeline
- 2026-08-02: disclosed: Initial publication by N-able
- 2026-08-02: patched: N-central 2026.3 Hotfix 1 released
- 2026-08-03: advisory: NVD publication date
- 2026-08-03: exploited: Reported as exploited in the wild in advisory metadata