Skip to main content

CVE-2026-18556N-able N-central Authentication Bypass Using an Alternate Path or Channel Vulnerability

Patch nowHigh8.2Exploited, CISA due date 2026-08-07EPSS 7.9%, higher than 95% of scored CVEs

CVE-2026-18556 is a authentication bypass by alternate path in N-able N-central, rated high (8.2 on CVSS 4.0).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

A second route to a protected function skips the sign-in check.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker act as a signed-in user, or an administrator, without valid credentials.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2026-08-04: it is being exploited in the wild. It can be exploited automatically, at scale. EPSS estimates a 7.9% chance of exploitation activity in the next 30 days, higher than 95% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2026-08-07.
  2. No fixed version is listed yet. Find every place N-able N-central runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  3. While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  4. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

Authentication bypass using an alternate path or channel vulnerability in N-able N-central allows Authentication Bypass.

This issue affects N-central: through 2026.1.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Sign-in, session and token handling. The flaw sits between anonymous callers and authenticated sessions.
  • Identity providers and SSO. The flaw sits between anonymous callers and authenticated sessions.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • Between anonymous callers and authenticated sessions. An attacker who crosses it can act as a signed-in user, or an administrator, without valid credentials.

Questions to answer about your own systems

  • Where does N-able N-central run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.