Quick answer
Yes. CVE-2026-18556 in N-able N-central is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on 4 August 2026. ASD's ACSC has also issued an alert. If you run N-central, apply the vendor's fix now and check for signs of compromise.
What is CVE-2026-18556?
N-able N-central Authentication Bypass Using an Alternate Path or Channel Vulnerability. N-able N-central contains an authentication bypass using an alternate path or channel that allows for authentication bypass.
Description from the CISA Known Exploited Vulnerabilities catalogue.
What kind of flaw is it?
A second route into the system skips the login check entirely.
Other exploited authentication bypass by alternate pathWhy it matters
Remote monitoring, management and support tools give administrators, and attackers, direct control of many machines at once. Managed service providers use them widely, so one exploited flaw can affect every client of a provider.
Higher than 99% of all scored vulnerabilities.
Am I affected? How to check | What to do now |
|---|---|
1Confirm whether you or your IT provider use the affected tool. | 1Apply the vendor fix and restrict access to the management console. |
2Check the server version and whether it is internet-facing. | 2Ask your managed service provider to confirm in writing that their instance is patched. |
3Review sessions, new accounts and deployed scripts for activity you do not recognise. | 3Enforce MFA on all remote management accounts. |
Am I affected? How to check
- 1Confirm whether you or your IT provider use the affected tool.
- 2Check the server version and whether it is internet-facing.
- 3Review sessions, new accounts and deployed scripts for activity you do not recognise.
What to do now
- 1Apply the vendor fix and restrict access to the management console.
- 2Ask your managed service provider to confirm in writing that their instance is patched.
- 3Enforce MFA on all remote management accounts.
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.
How fast to patch
Under the Essential Eight, patches for internet-facing services should be applied within 48 hours when a working exploit exists, and higher maturity levels apply the same 48-hour target to applications such as browsers and office software. A vulnerability in this catalogue has, by definition, been exploited in the wild, so treat it as the 48-hour case.
Australian Signals Directorate alerts
In the news
- N-able Patches 17 N-central Flaws as Attackers Exploit Earlier Bugs to Deploy Crypto MinersThe Hacker News · 17 November 2026
- Patch Now! Hackers targeting critical vulnerability impacting Atlassian & N-able productsCyber Daily · 16 November 2026
- ⚡ Weekly Recap: N-able 0-Days, Windows 0-Days, Chrome 0-Days, Fridge 0-Days, and More Bad DaysThe Hacker News · 16 November 2026
- New N-able "4EverAble2Shell" zero-day exploited hours after PoC releasedBleepingComputer · 12 November 2026
- N-able takes cloud service offline, says customers should follow suit, following mass vulnerability disclosureCyber Daily · 11 November 2026
More in the daily briefing.
Common questions
Is CVE-2026-18556 being exploited?
Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on 4 August 2026.
How do I fix CVE-2026-18556?
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. Check the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.
Is my N-able N-central affected?
Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.