CVE-2026-18577: N-able N-central Authentication Bypass Using an Alternate Path or Channel
N-able N-central · listed in the CISA catalog of actively exploited vulnerabilities since 2026-08-03.
- CVSS v4.0 (CVE record)
- 8.2
- high
- EPSS (exploit probability, 30 days)
- 15%
- higher than 96.7% of all CVEs
- Added to CISA KEV
- 2026-08-03
- US federal due date 2026-08-06
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2026-18577 explained
CVE-2026-18577 is an authentication bypass in N-able N-central server software. It stems from an incomplete patch for CVE-2026-18556 and allows authentication bypass and account takeover. CISA lists it as known exploited, so exposed N-central servers need prompt attention.
Impact
An attacker can bypass authentication and take over accounts in N-central. CISA rates the flaw as automatable, meaning it can be exploited at scale without manual steps. CISA also rates the technical impact as total, meaning full control of the affected component or full disclosure of its information. Attackers are known to use this vulnerability. Whether it is used in ransomware campaigns is unknown.
Who is affected
The CVE record lists N-able N-central versions ≤ 2026.3 as affected. The description states that versions through 2026.3.1 are affected. The record names 2026.3.1.7 as the version that contains the fix. Treat any installation older than 2026.3.1.7 as potentially vulnerable, including systems that applied the earlier fix for CVE-2026-18556.
Written with AI from the data on this page and checked against it automatically.
Official description
An incomplete patch for CVE-2026-18556 allows for authentication bypass and account takeover in N-central Versions through 2026.3.1
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
- documentation.n-able.com/N-central/Release_Notes/GA/Conte…
- status.n-able.com/2026/08/02/n-central-2026-3-hotfix-1-mi…
- BOD 26-04: cisa.gov/news-events/directives/bod-26-04-prioritizing-se…
- Forensics Triage Requirements: cisa.gov/news-events/directives/bod-26-04-implementation-…
- nvd.nist.gov/vuln/detail/CVE-2026-18577
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- N-able N-centralAffectedFixed in
- ≤ 2026.3
- 2026.3.1.7
| Product | Affected | Fixed in |
|---|---|---|
| N-able N-central |
|
|
How to fix it
- Update to a fixed version: 2026.3.1.7.
- Vendor advisory: documentation.n-able.com/N-central/Release_Notes/GA/Conte…
- CISA's deadline for US federal agencies: 2026-08-06 (passed) – a useful benchmark for everyone else, too.
What to do
- Update N-able N-central to
2026.3.1.7or later. - Follow the N-able vendor advisory and apply any mitigations it describes.
- Do not rely on the earlier fix for CVE-2026-18556 alone; it is incomplete.
- Restrict network access to N-central servers and keep administrative interfaces off the internet where possible.
- Check for signs of compromise, such as unexpected account changes or logins, and follow CISA's forensics triage requirements.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-288 Authentication bypass using an alternate path or channel
Questions about CVE-2026-18577
- We already patched CVE-2026-18556. Are we safe?
- Not necessarily. CVE-2026-18577 exists because the patch for CVE-2026-18556 was incomplete. Update to
2026.3.1.7or later. - Is this vulnerability being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-08-03, with a US federal due date of 2026-08-06. Whether it is used in ransomware is unknown.
- What does CISA require?
- Apply mitigations according to vendor instructions, follow BOD 26-04 guidance and CISA's forensics triage requirements, and discontinue use of the product if mitigations are unavailable. Assess each asset's internet exposure.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.