Status note: This article reflects public information available on 19 November 2026. N-able's investigation is still ongoing, so some details may change. Check N-able's official status page for the latest updates.
Summary
N-able, a vendor of IT management and security software for managed service providers (MSPs), has confirmed that an unauthorized party accessed one of the servers in its Mail Assure and SpamExperts Hosted Cloud environment. In response, N-able disabled the management portal (UI) and API access for both products in three regions: the Americas, Europe and Asia-Pacific (APAC).
According to N-able, email delivery and spam filtering kept working. Administrators, however, lost access to the dashboard, the API, quarantine and logs while the company investigated and rebuilt the affected services.
What happened
The problem first appeared as a service disruption. N-able first attributed it to "platform configuration and service dependencies" in the Mail Assure and SpamExperts Hosted Cloud environment. As the investigation continued, the company revised that assessment and said the disruption was caused by a security incident involving unauthorized access to one of the servers in the environment.
N-able said it had "taken steps to mitigate the threat" and is "continuing to harden" its services to reduce the risk of recurrence. N-able has also said the incident is unrelated to the separate N-central security issues disclosed earlier in November 2026.
At the time of writing, N-able has not publicly disclosed:
- who was behind the attack,
- how the attacker got in (no CVE or vulnerability has been named for this incident),
- how long the attacker had access.
Affected services and regions
| Product | Regions |
|---|---|
| Mail Assure | Americas, Europe, APAC |
| SpamExperts Hosted Cloud | Americas, Europe, APAC |
What kept working and what did not
| Function | Reported status (19 Nov 2026, 08:00 UTC) |
|---|---|
| Inbound and outbound mail flow | Operating |
| Inbound and outbound spam filtering | Operating |
| Management portal / dashboard (UI) | Disabled |
| API access | Disabled |
| Quarantine | Offline, pending validation |
| Logging | Offline, pending validation |
Timeline
All dates are 2026. The timeline is based on N-able's status page as reported by the security news outlets listed under Sources.
- 16 November: N-able first notified customers of a service disruption affecting Mail Assure and SpamExperts Hosted Cloud.
- 17 November: N-able attributed the disruption to platform configuration and service dependencies and began restoration work.
- 18 November: N-able revised its assessment and confirmed unauthorized access to one of the servers. UI and API access were proactively disabled. Later that day, N-able said it had emailed partners directly with information specific to their environment and instructions on whether they needed to act.
- 19 November: N-able said each service must pass security validation in a controlled environment before it returns. As of 08:00 UTC, mail flow and filtering were operating, while the portal and API remained disabled and quarantine and logging were still being validated. The incident was widely reported by security news sites the same day.
Impact on customers and email security management
For end users, email kept arriving and being filtered. The impact fell mainly on the people who manage the service, usually MSPs and IT administrators. While the portal and API were offline, they could not:
- sign in to the Mail Assure or SpamExperts dashboard,
- review or release quarantined messages, including false positives that users were waiting for,
- check delivery and filtering logs when investigating a missing email or a suspicious message,
- change configuration, such as adding domains or adjusting filtering rules,
- run API-based automation and integrations that depend on the service.
On customer data, N-able said that "at this time" it does "not have evidence that customer data was compromised, including access to tenants' mailboxes." This is an interim finding from an investigation that is still open, not a final conclusion. Some headlines have mentioned "credential exposure", but N-able's public updates have not confirmed that any passwords, API keys or tokens were exposed. Treat that point as unconfirmed.
What N-able has said and done
- Confirmed unauthorized access to one server in the Mail Assure and SpamExperts Hosted Cloud environment.
- Proactively disabled management UI and API access in all three regions.
- Kept mail flow and filtering running.
- Required each service to pass security validation before it is brought back online.
- Contacted affected partners directly by email with environment-specific information and instructions.
- Stated it is continuing to harden its services to reduce the risk of recurrence.
Practical steps for MSPs and IT admins
1. Check whether you are affected
- Confirm whether you or your clients use Mail Assure or SpamExperts Hosted Cloud, and in which region (Americas, Europe or APAC). Self-hosted or other email filtering products were not named in N-able's notices.
- Look for N-able's direct email about this incident in your partner inbox (and in spam folders). It says whether you need to take action.
- Follow the official N-able status page for updates rather than third-party summaries.
- If you are unsure, contact N-able Technical Support through your usual, verified support channel.
2. Manage the outage
- Tell your clients that email delivery and filtering are working, but quarantine releases and configuration changes are delayed.
- Keep a list of quarantine release requests and configuration changes you need to make, so you can process them once the portal is back.
- Pause or monitor API-based scripts and integrations so they do not fail silently or flood your alerting.
- Keep your own records, such as mail-server logs and the times of failed portal or API attempts, in case you need them later.
3. Watch for phishing that uses the incident
Attackers often take advantage of well-known incidents. Be careful with unexpected emails about "password resets", "quarantined messages waiting for release" or "urgent security actions" that claim to come from N-able. Do not click links in these messages. Check any request through N-able's official status page or your known support contacts.
4. When access is restored
N-able has not issued a public, blanket instruction to reset credentials. As a precaution, and following any specific instructions N-able sends you, consider:
- changing admin and sub-admin passwords for the portal,
- rotating API keys and any credentials used by integrations,
- making sure multi-factor authentication is enabled where it is available,
- reviewing user and admin accounts for anything you do not recognize,
- comparing domain settings, filtering rules, allow lists and outbound settings against your last known good configuration,
- asking N-able in writing whether any configuration in your environment changed during the incident, and requesting a summary of their investigation once it is complete.
5. Lessons learned
- Plan for losing the management plane. Mail kept flowing, but no one could manage it. Your incident runbooks should cover what to do when a vendor portal or API is unavailable for several days.
- Keep configuration backups outside the vendor. A documented copy of domains, routing and filtering rules makes it much easier to check for changes after an incident.
- Know your vendor contact paths. Make sure the right people receive vendor security notices, and subscribe to vendor status pages.
- Read the first explanation with caution. In this case, an outage first described as a configuration issue was later confirmed as a security incident. Early statements can change as investigations progress.
- Prepare client communication templates. Clear, early messages to clients reduce support load and build trust during third-party incidents.
What is still unknown
As of 19 November 2026, the attacker's identity, the method of entry, the length of the access, and whether any credentials were exposed have not been publicly confirmed. N-able's statement about customer data is based on the evidence available so far. We will not speculate on these points. Follow N-able's official updates for confirmed information.
Sources
- N-able Status Dashboard: Mail Assure and SpamExperts Hosted Cloud incident
- The Hacker News: Hackers Breach N-able Cloud Server, Disrupting Email Security Management Across 3 Regions
- Cyber Security News: N-able Confirms Server Breach, Disables Mail Assure and SpamExperts Management Access
- GBHackers: N-able Confirms Security Breach in Mail Assure and SpamExperts Hosted Cloud
- Cyber Press: N-able Confirms Cyberattack on Mail Assure and SpamExperts Cloud
- Brandefense: N-able Mail Assure Incident: Service Matrix
