SecureCyberVM
CVE Lookup Daily Threat Briefing Exploited CVEs Ransomware Zero-day
SecureCyberVM
Get the Patch Brief

N-able confirms server breach behind Mail Assure and SpamExperts cloud outage

N-able has confirmed that a global outage of its Mail Assure and SpamExperts Hosted Cloud services was caused by unauthorized access to one of its servers. Mail flow continued, and the company says it has no evidence customer data was compromised.

N-able confirms server breach behind Mail Assure and SpamExperts cloud outage

N-able has confirmed that a worldwide outage of its Mail Assure and SpamExperts Hosted Cloud email security services was caused by attackers gaining access to one of its servers, according to BleepingComputer. The disruption affected customers in the Americas, Asia-Pacific and Europe.

The disclosure adds to a difficult month for the managed service provider software vendor, whose N-central remote monitoring and management platform has been the subject of dozens of publicly released zero-day exploits and active attacks. N-able says the two incidents are not related.

What happened

According to BleepingComputer, N-able initially attributed the outage earlier in the week to a combination of platform configuration and service dependencies. A day later, the company disabled user interface and API access and confirmed unauthorized access to one of the servers in the Mail Assure and SpamExperts Hosted Cloud environment.

After detecting the intrusion, N-able notified customers by email and took several services offline: the management portal, quarantine, logging and mailbox synchronization. The company said it had taken steps to mitigate the threat and was continuing to harden its services.

N-able has not disclosed how the attackers gained access, when the intrusion began, who was responsible, how long the server was accessible, or whether any data left its environment.

Who is affected

The incident affects organizations, many of them managed service providers and their clients, that use the Hosted Cloud versions of Mail Assure and SpamExperts for inbound and outbound email filtering. According to N-able, email flow and spam filtering continued to work throughout. Until access is restored, however, customers may be unable to sign in to the dashboard, view or release quarantined messages, review logs, or add and remove domains, BleepingComputer reported.

N-able has not said how many customers or tenants are served by the affected server, or whether other servers in the platform were examined and found clean. A restoration timeline was not disclosed in the reporting.

Severity and exploitation

No vulnerability or CVE has been tied to the intrusion, and the initial access method has not been disclosed. N-able told customers it has no evidence that customer data was compromised, including any access to tenant mailboxes, and that its investigation is ongoing.

The risk profile is nonetheless significant. Email filtering services sit in the mail path for every protected domain and hold quarantined messages, logs and configuration for many downstream organizations. Access to such a platform could, in principle, expose message metadata or quarantined content, or allow tampering with filtering rules. None of these outcomes has been reported, and N-able’s current position is that customer data was not affected.

The company stressed that the incident is separate from the N-central situation, in which it took hosted N-central environments offline to address more than 30 publicly released zero-day flaws. In that campaign, attackers exploited a chain dubbed 4EverAble2Shell, which uses the Apache Axis flaw CVE-2026-90436, to deploy cryptocurrency miners on N-central servers, according to BleepingComputer.

What defenders should do now

  1. Follow N-able’s status page and customer emails for restoration notices and any change in its data-compromise assessment.
  2. Rotate API keys, service credentials and any SMTP or integration credentials configured in Mail Assure or SpamExperts once access is restored.
  3. Review the platform’s domain list, filtering rules, allow lists and outbound routing after restoration and compare them against known-good configuration.
  4. Monitor inbound mail closely for phishing or malware that could pass through altered filtering, and keep secondary filtering such as mailbox-level protections enabled.
  5. Managed service providers should inform affected clients that management features are unavailable and document the incident for their own compliance records.
  6. Organizations also running N-central should continue to apply N-able’s separate N-central guidance, including keeping the Legacy API disabled.

SCVM analysis

The initial description of the outage as a configuration problem, followed a day later by confirmation of an intrusion, illustrates how vendor communications can shift as investigations develop. Customers relying on hosted security services have limited visibility into incidents like this and depend on the vendor’s own findings. Until N-able discloses the access method and scope, defenders should treat the platform’s stored configuration and credentials as potentially exposed and verify them, even though the company reports no evidence of data compromise. The concentration of incidents across N-able products also makes this a timely moment for MSPs to review their dependency on single vendors for both management and email security.

Sources

About this article: produced by the SCVM Newsroom with AI assistance from the public sources linked above, enriched with NVD, FIRST EPSS and CISA KEV data, and checked by automated quality controls under our editorial policy. Spotted an error? Request a correction.

SecureCyberVM

Install SecureCyberVM

Get the Daily Threat Briefing and exploited-CVE alerts one tap away, full screen, like an app.