SAASMENT

News

Attackers reached an N-able mail-security cloud server.

N-able says unknown attackers got into one Mail Assure and SpamExperts Hosted Cloud server and took management portals and APIs offline. The company says it has no evidence that customer mailboxes were opened.

Illustration of lime arrows passing through a cloud server whose pink management panel is broken

Impact

What was impacted
One server in N-able’s Mail Assure and SpamExperts Hosted Cloud. The intrusion led N-able to disable management interfaces and APIs. Still affected, as of the November 19 disclosure: Mail Assure and SpamExperts in the Americas, APAC, and Europe. The management portal, APIs, quarantine, and logging are offline. Core mail flow and inbound and outbound filtering are still available.
Who was impacted
Partners and customers of Mail Assure and SpamExperts Hosted Cloud in those three regions. N-able says it contacted those partners about whether they need to act. This incident is separate from the N-central bugs referred to as Able2Shell, 4EverAble2Shell, and Agent2Shell.
What you need to do
Read the notice N-able sent for your environment and follow only the actions it lists. Do not assume mailboxes were accessed: the investigation is ongoing, and N-able says it has no evidence of customer-data compromise, including mailbox access. Plan for the portal, APIs, quarantine, and logging to stay down until N-able finishes validation. Mail filtering is still up, so do not remove the service on the basis of this disclosure alone.

N-able disclosed that unknown attackers gained unauthorized access to one server in the Mail Assure and Spam Experts Hosted Cloud. That access is what led the company to disable management interfaces and APIs. N-able said it has taken steps to contain the threat and is hardening the service. The investigation is ongoing. At the time of the disclosure, the company said it had no evidence that customer data was compromised, including access to tenants’ mailboxes.

The trail starts with a service disruption on November 16, 2026. N-able first traced it to platform configuration and service dependencies inside the hosted cloud. It later determined the disruption was a security incident. Restoration is underway in every region. Core mail flow and inbound and outbound filtering remain available. The management portal, APIs, quarantine, and logging stay offline until validation is finished.

Services still affected are Mail Assure and SpamExperts, each in the Americas, APAC, and Europe. N-able said it has contacted those partners with information about their environment and whether they need to do anything. As of November 19, 2026, at 8 a.m. UTC, restoration was still in progress, including validation and hardening of the management portal and the services behind it.

N-able said this incident is unrelated to vulnerabilities in N-central referred to as Able2Shell, 4EverAble2Shell, and Agent2Shell. The disclosure does not name the attackers, the entry point, or a CVE. Treat it as a developing incident and take next steps from the partner notice, not from guesses about mailbox access.

For your AI agent

Agent instructions — copy paste to Claude

You are helping me respond to N-able's disclosure that unknown attackers gained unauthorized access to one server in the Mail Assure and SpamExperts Hosted Cloud. That access led N-able to disable management interfaces and APIs. This is a developing incident. Do not invent an entry point, a CVE, or evidence of mailbox access.

Facts from the disclosure:
- N-able said it has contained the threat and is hardening the service. The investigation is ongoing. As of the disclosure, N-able said it had no evidence that customer data was compromised, including access to tenants' mailboxes.
- A service disruption on November 16, 2026 was first traced to platform configuration and service dependencies, then determined to be this security incident.
- Still affected: Mail Assure and SpamExperts, each in the Americas, APAC, and Europe.
- Core mail flow and inbound and outbound mail filtering remain available.
- The management portal, APIs, quarantine, and logging remain offline until N-able finishes validation.
- As of November 19, 2026, at 8 a.m. UTC, restoration was still underway.
- N-able said it contacted Mail Assure and SpamExperts Hosted Cloud partners with information about their environment and whether action is required.
- N-able said this incident is unrelated to N-central vulnerabilities referred to as Able2Shell, 4EverAble2Shell, and Agent2Shell.

Context:
- What was impacted: one hosted mail-security server, and the management portal, APIs, quarantine, and logging for Mail Assure and SpamExperts Hosted Cloud.
- Who should care: partners and customers of those services in the Americas, APAC, and Europe.
- What to do: follow the partner notice N-able sent. Do not assume mailboxes were opened.

Do this in order. Ask before changing mail routing, DNS, or security-product settings. Prefer read-only inventory first. Do not write or run an exploit.

1. Inventory
   - Record whether this environment uses Mail Assure or SpamExperts Hosted Cloud, and which region.
   - Record whether the management portal, API, quarantine, or logging is currently unavailable.
   - Confirm mail flow and inbound and outbound filtering are still passing mail, using read-only checks.
   - Find the notice N-able sent to partners. Quote only actions that notice actually lists. If you do not have the notice, say so and stop before recommending customer-side changes.
   - Keep this separate from N-central Able2Shell, 4EverAble2Shell, and Agent2Shell. Those are a different issue.
2. Contain
   - If the partner notice names a containment step, propose that step and ask before applying it.
   - If the notice says no action is required, say that, and do not add extra blocks on mail flow.
3. Remediate
   - Plan only the actions in N-able's notice. The disclosure does not name a patch version. Do not invent one.
   - Expect the management portal, APIs, quarantine, and logging to stay down until N-able completes validation.
4. Verify
   - Recheck that filtering still works and record the status of the portal and APIs.
5. Report back
   - Which products and regions you found, what the partner notice asked for, what you changed, and what N-able still has offline.

Do not invent attackers, stolen data, or CVEs. If a check needs access I have not given you, say what you need and stop.

← All news

Try the platform.

Open the demo workspace with mock data. No login. Register from the banner when you want early access. No security team. No call.

Try the platform