Skip to content

Applications

CVE-2026-91000

Missing authentication in N‑able N-central allows local privilege escalation.

Major vulnerability. RMM product used by MSPs; local privilege escalation could allow widespread administrative takeover of managed endpoints and customer environments.

CVSS
8.4Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.20%chance of exploitation in the next 30 daystop 91% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
10 Nov 2026analysed here 12 Nov 2026

Summary

Impact

Local or low-privileged actors can escalate to admin/SYSTEM via insecure IPC channels, enabling full control of N-central and managed endpoints.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
N-able N-central< 2026.4.1Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • N-able N-central < 2026.4.1

Fix and mitigation

Action required

Immediate action required

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 11 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 10 Nov 2026Published
  2. 11 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 12 Nov 2026CVE record last updated1 day later
  4. 12 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-91000 being exploited?

Not confirmed. CVE-2026-91000 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.

How severe is CVE-2026-91000?

CVE-2026-91000 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-91000?

Yes. A fix has been recorded for CVE-2026-91000. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-91000 affect?

CVE-2026-91000 affects N-able N-central < 2026.4.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-91000?

Upgrade N-central to 2026.4.1+, restrict local access, and audit logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Advisories (1)

  • me.n-able.com /s/security-advisory/aArVy0000002irNKAQ/cve202691000-insecure-ipc-channels-lead-

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com