Skip to content

Data Breaches

N-able confirms one-server breach disrupted Mail Assure and SpamExperts worldwide

N-able said the disruption started Nov. 16, 2026, and that inbound and outbound email filtering continued operating normally.

https://breach-signal.com/data-breaches/n-able-server-breach-disrupts-mail-assure-spamexperts/

Share

Key facts

  • N-able confirmed that attackers breached one of its servers, causing a major worldwide outage of Mail Assure and SpamExperts Hosted Cloud email-security services.
  • The email-security outage that N-able investigated started on November 16, 2026.
  • N-able originally blamed the outage on platform configuration and links between services across the Americas, Asia-Pacific, and Europe.
  • On November 18, 2026, at 03:05 UTC, N-able said its investigation determined that a security incident lay behind the disruption.

N-able confirmed that attackers breached one of its servers, causing a major worldwide outage of Mail Assure and SpamExperts Hosted Cloud email-security services that began Nov. 16, 2026.

The company initially pointed to platform configuration problems and connections between services spanning the Americas, Asia-Pacific, and Europe on Nov. 16 and 17, 2026. At 03:05 UTC on Nov. 18, 2026, N-able reversed that explanation and said its investigation determined a security incident lay behind the disruption.

N-able’s probe found that the incident involved a single web server and that someone without authorization might have reached certain credentials stored there. The company’s public updates did not confirm actual credential exposure or identify affected passwords, application programming interface keys, or tokens. The company’s statement to CRN did not specify how the intruder gained entry or how many customers the intruder may have affected.

Throughout the incident, inbound and outbound email continued moving normally, and spam filtering remained active, so customers could send and receive filtered messages. After detecting the attack, the company shut down management dashboards, application programming interfaces, quarantine tools, logging, and mailbox synchronization in the Americas, Asia-Pacific, and Europe. Management dashboards, application programming interfaces, quarantine systems, and logging have been offline since Nov. 17, 2026. According to the status page, six components are affected: Mail Assure and SpamExperts Hosted Cloud across the Americas, Europe, and Asia-Pacific.

Although customers in all three regions lost portal and application programming interface access, N-able confirmed compromise of only a single server. The loss of management access does not mean a breach hit servers in each region.

To date, the company’s investigation has turned up no evidence that anyone viewed customer data or tenant mailboxes. “We are aware of unauthorized access to one of the servers in the Mail Assure and SpamExperts Hosted Cloud,” N-able said. N-able called the finding part of an ongoing probe, not a final conclusion. The company has not disclosed how the intruder got in, how long the access lasted, or who carried it out.

N-able powered down the affected server, rotated internal credentials, and revoked customer application programming interface and OAuth tokens. It also told local users to create new passwords ahead of time. A Nov. 17, 2026 update said fixing the problem would involve rebuilding affected infrastructure and refreshing several platform components. N-able kept email delivery and spam filtering running while it took the management portals and APIs offline for the duration of the probe.

The company said every affected component will come back only after passing security checks in a controlled setting, and the company has not scheduled a full restoration.

Starting at 00:01 UTC on Nov. 19, 2026, N-able ran tests on some fixes in a controlled setting, and engineers were still working through those tests and security changes by 04:01 UTC. By 8:06 a.m. UTC on Nov. 20, 2026, N-able said remediation work had moved forward, with engineers handling remaining items and re-testing measures completed earlier.

On Nov. 20, 2026, N-able said email delivery and filtering were still working fully, while access to the portal and application programming interfaces remained disabled pending security validation. The company said it will post more updates to its status page as new information becomes available.

With the services down, customers cannot sign in to the dashboard or change settings such as domain additions and removals. They also cannot open, release, or view held quarantine messages, and logs are unavailable. Continued mail delivery does not reveal whether anyone held an individual message, and the missing portal restricts what support teams can verify.

For managed service providers that resell the services, the outage prevents the release of legitimate email sitting in quarantine, and providers cannot look at filtering logs for the accounts they manage. Messages such as invoices, password resets, and replies to marketing campaigns may remain unread for days, and tracing bounced or rejected messages is more difficult without logging.

People sending messages to domains protected by Mail Assure or SpamExperts cannot have held email released, and recipients may not realize a message arrived. Senders who notice unexplained silence from small business recipients and no bounce message should treat this incident as a possible explanation.

N-able sent email to affected customers and gave partners configuration guidance specific to how each one reaches and sets up Mail Assure or SpamExperts Hosted Cloud. Partners who never received the company’s direct email should reach out to N-able Technical Support and should not assume their environment was unaffected. N-able said it reached out to affected partners directly after establishing the cause, and it said customers should delay domain or routing changes until the portal is back and passes validation.

The company’s public notice did not order a general credential reset for customers, and its public updates did not confirm exposure of any specific secrets. Teams should rely on N-able’s updates and environment-specific instructions instead of assuming that working email delivery means management access has returned.

Because email-filtering services sit in the path of messages for every tenant, the infrastructure is a concentrated target. One provider’s server can reach many downstream organizations at once, particularly when managed service providers operate the service for their customers.

N-able said the email-security incident has nothing to do with the separate N-central remote monitoring and management platform incident. During that earlier event, N-able pulled its hosted N-central systems offline on Nov. 9, 2026, and restored them after an emergency update on Nov. 10, 2026, that patched seven CVEs. N-able pulled its remote monitoring and management and unified endpoint management platform offline to build and distribute patches for dozens of zero-day flaws (previously unknown security vulnerabilities) that a researcher posted on GitHub.

BleepingComputer reported that patching for the N-central incident covered more than 30 zero-day flaws, while CRN said the update addressed seven CVEs. N-able tied the N-central incident to zero-day flaws including Able2Shell, 4EverAble2Shell, and Agent2Shell.

Attackers are using a newly disclosed N-able zero-day called 4EverAble2Shell to install cryptocurrency miners on vulnerable N-central servers, BleepingComputer said. According to a post from Huntress, combining the Able2Shell flaws can allow remote code execution or privilege escalation on affected N-central servers.

Wilhelm Rebmann, chief technology officer at Telford, Pa.-based Altek Business Systems, said redundancies are worth paying for and retaining, though available alternatives did not replace every capability missing during the N-central shutdown. “We don’t have redundancy of everything,” he said.

N-able is dealing with two security issues at the same time, and customers reviewing the response face two separate question groups: one about the N-central flaws and one about the hosted email-filtering infrastructure. About two days elapsed from N-able’s first look at the problem to its confirmation that a security incident was responsible.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *