A cloud email security system blocks suspicious messages, with warning, lock, and threat icons protecting servers.
N-able has changed its account of the disruption to its hosted email security platform. A problem it first blamed on configuration is now a confirmed security incident. The company says an unauthorized party got into one server in the Mail Assure and SpamExperts Hosted Cloud environment. The breach caused a major outage of management tools in every region the services cover. Many MSPs and web hosts use these filters in front of Microsoft 365 and other mailboxes. For them, the key point is that mail is still moving, but administrators can't do much with it.

A cloud email security system blocks suspicious messages, with warning, lock, and threat icons protecting servers. Timeline: from "configuration issue" to confirmed intrusion​

N-able first talked about the problem as an ordinary operations fault. According to BleepingComputer, the company initially blamed the outage on what it described as a "combination of platform configuration and service dependencies" affecting Mail Assure and SpamExperts services across the Americas, Asia-Pacific, and Europe.

That explanation didn't last long. N-able later said: "Our earlier update said the disruption came from platform configuration and service dependencies and we believed we had remediated the issue. As we continued our investigation, we determined that the disruption was caused by a security incident affecting the Mail Assure and SpamExperts Hosted Cloud environment"

Here is the sequence, pieced together from N-able's status updates as reported by several outlets:

  • November 16: N-able first told customers about a service disruption in the hosted email security environment.
  • November 17, 03:00 UTC: The formal status incident opened. The company lists the email incident as a major outage under event ID 202672. The Cyber Security Guru noted that the November 17 update came before the incident was reclassified as a security event. Even so, it already said remediation required "rebuilding affected infrastructure and updating several platform components."
  • November 18: The company revised that assessment at 03:05 UTC on November 18, attributing the disruption to a security incident and disclosing the unauthorized server access.
  • November 19: By 00:01 UTC, N-able had begun testing some remediation measures and said each affected service would have to pass security validation in a controlled environment before returning to production. The Hacker News reported that at 08:00 UTC the same day, restoration was still under way and portal and API access were still disabled.
  • November 20, 08:06 UTC: According to The Hacker News, N-able said remediation had moved forward and engineers were working through the remaining items. Email was still flowing and filtering normally, and portal and API access stayed disabled as a precaution.

As of the most recent reporting, the incident remains classified as a major outage, with its status marked as identified.

Section summary: N-able took about two days to call this a security incident. Restoration was still in progress on November 20.

What still works and what doesn't​

This isn't a "your email is down" outage. N-able said the cyberattack didn't affect email flow or spam filtering and that it has yet to find evidence that the attackers gained access to customers' data and mailboxes.

The admin side is a different matter. After detecting the attack, N-able also alerted customers via email and took down the management portal (dashboard), as well as quarantine, logging, and mailbox synchronization supporting services. N-able said that until those services come back, customers may not be able to:

  • sign in to the control panel
  • view or release quarantined messages
  • review logs
  • make configuration changes, such as adding or removing domains
FunctionStatus per N-able's updates
Inbound mail filteringOperating
Outbound mail filteringOperating
Mail deliveryOperating
Management portal (UI)Offline
API accessDisabled
QuarantineOffline
LoggingOffline
Mailbox synchronizationOffline

The affected regional services are the same for both products. The Hacker News lists Mail Assure and SpamExperts in the Americas, APAC and Europe.

That split is what matters day to day. Brandefense put it this way: teams can keep routing mail through the hosted filtering service, but they need temporary procedures for quarantined messages, configuration requests and workflows that depend on the portal or API. If a client's invoice lands in quarantine, nobody can release it right now. Mail is still being filtered, but admins can't see or change much.

Section summary: Mail is still being delivered and filtered. Quarantine, logs, configuration and API automation are unavailable.

The credential question​

The biggest open question is about credentials, and the reporting doesn't fully agree.

SecurityWeek says N-able told it the incident was limited to a single web server, where an unauthorized party "may have been able to access certain credentials stored on the platform." SecurityWeek also reports that N-able took several containment steps:

  • took the affected server offline
  • rotated internal platform credentials
  • revoked existing customer API tokens
  • invalidated OAuth tokens
  • reset passwords for local users as a precaution

Other outlets read the public status updates more narrowly. GBHackers reported that the company has not confirmed whether any credentials were exposed. CyberPress said the public incident updates did not confirm credential exposure or identify any affected passwords, API keys, or tokens.

The two accounts can both be true. N-able's public status page sticks to "no evidence of compromise." Its statement to SecurityWeek allows that stored credentials may have been reachable. Either way, the response measures it describes point to a precautionary credential rotation across the platform. Possible exposure is not the same as confirmed theft, and nothing published so far shows that any credentials were actually taken or used.

Mail Assure's own documentation shows why OAuth secrets matter here. Administrators set up OAuth/SSO by entering a client ID and client secret from their identity provider, such as Microsoft 365 or Google Workspace. If those values were stored on an affected system, rotating them on the identity-provider side is a sensible step. Whether that applies to your tenant depends on N-able's guidance for your environment, not on a general rule.

Section summary: N-able has confirmed precautionary resets of tokens and passwords. It has not confirmed that credentials were stolen.

What administrators should do now​

N-able told SecurityWeek it has given customers specific guidance based on how they access and configure Mail Assure or SpamExperts Hosted Cloud. The Hacker News also reports that partners were contacted directly with information about their environment and whether they need to act. So start there.

  1. Find N-able's direct notice. Check the mailboxes your organization uses for vendor or partner communications. The notice should tell you whether your environment needs action.
  2. Expect broken API integrations. N-able reportedly revoked existing customer API tokens, so scripts, PSA connectors or provisioning tools that call the Mail Assure/SpamExperts API will probably need new credentials once API access is back.
  3. Plan for local-user password resets. Local accounts had their passwords reset proactively, so plan a re-onboarding process for admins and end users who sign in to the control panel.
  4. Review OAuth/SSO configurations. If you use OAuth login, ask N-able whether you need to rotate the client secret at your identity provider. Then update the setting in the product once UI access returns.
  5. Set up a temporary quarantine process. Tell helpdesk staff and clients that held messages can't be released until quarantine is restored. That way a missing email doesn't turn into a P1 ticket.
  6. Hold off on domain changes. Adding or removing domains isn't possible right now, so delay onboarding, offboarding or migration work that depends on it.
  7. Monitor N-able's status page. Watch incident 202672 for restoration updates instead of assuming services are back.

Don't do mass resets that N-able hasn't asked for. Rotating everything in sight feels good, but it can create more outage than the original incident did.

Not the N-central incident​

The timing will confuse people. N-able is also dealing with serious problems in N-central, its remote monitoring and management platform. BleepingComputer notes that N-able took all hosted N-central environments offline to patch more than 30 zero-day flaws. It also reports that attackers are exploiting a newly disclosed N-central zero-day called "4EverAble2Shell" to deploy cryptocurrency miners.

N-able says the two events are separate. The company explicitly stated that this incident was unrelated to the separate N-central incident, distinguishing the affected hosted email environment from its remote monitoring and management platform. Nothing published so far links the N-central vulnerabilities to how the Hosted Cloud server was accessed. Assuming a link would be speculation.

Analysis: what this incident shows​

First diagnoses aren't final. It's easy to criticize N-able for calling an intrusion a configuration problem. In fairness, The Cyber Security Guru argued that misattribution like this is common, and in this architecture it is nearly predictable. A compromised server often looks like a broken dependency at first. Still, customers who saw "configuration issue" on day one had no reason to review their credentials. The early wording matters.

Mail flow doesn't tell you much about security. CyberPress put it well: uninterrupted mail flow does not establish whether administrative systems or credentials were accessed. When you monitor an email security vendor, a green status for delivery tells you about message handling. It tells you nothing about the admin side.

Many affected customers may not know they use N-able. A DEV Community post pointed out that if your business email is cleaned by a filter your web host or IT provider set up, you may never have seen the brand name behind it. Small businesses with frozen quarantines may need their provider to explain why. This is a good time to find out which vendors sit between your MX records and your Microsoft 365 tenant.

What we still don't know: who the attackers were, how they got in, how long they had access, whether any credentials were actually taken, and how many customers are affected. N-able's investigation is ongoing. Until it publishes more, assume the incident is still open.

Restoring the dashboard after validation will be the first milestone. The more important one will be a post-incident report that explains how one web server came to hold credentials worth rotating across the whole platform.

 

References

  1. N-able says recent security breach led to major service outage BleepingComputer 2026-11-20T08:18:36-05:00
  2. N-able Confirms Security Breach in Mail Assure and SpamExperts Hosted Cloud, Credentials Potentially Exposed gbhackers.com
  3. N-able Confirms Cyberattack on Mail Assure and SpamExperts Cloud, Warns of Credential Exposure cyberpress.org