N-able confirms Mail Assure and SpamExperts Hosted Cloud server intrusion
N-able confirms unauthorized server access in Mail Assure and SpamExperts Hosted Cloud, separate from N-central. Mail flow and filtering continue, while management, API, quarantine and logging remain offline. Partners are being emailed environment-specific instructions.
- Disclosed
- Nov 18, 2026
- Updated Nov 19, 2026
- Severity
- Septic Tank Blew
- No CVE: a breach, not a bug
- Splash zone
- Mail Assure and SpamExperts Hosted Cloud partners across the Americas, APAC and Europe
- N-able · SaaS · Email · Intrusion
- In the wild
- Yes
- N-able confirms unauthorized access to a server in the hosted environment.
What happened
N-able’s public status record corrects its earlier operational explanation: unauthorized access occurred on one server in the Mail Assure and SpamExperts Hosted Cloud environment. The vendor says this is unrelated to the N-central incident. Its November 18 security confirmation is distinct from the earlier service disruption and the status record’s November 17 start time.
At 03:05 UTC on November 18, N-able said it had no evidence at that time that customer data, including tenants’ mailboxes, had been compromised. This was a point-in-time investigation statement, not proof that no exposure occurred. Later public updates continue the investigation without establishing a victim count, an entry vulnerability, a credential-exposure inventory or a final data-impact assessment.
The 20:18 UTC update says inbound and outbound mail flow and filtering have continued throughout. The management portal, APIs, quarantine and logging remain offline while restoration is validated. Earlier updates also identify mailbox synchronization among supporting services being restored. These availability statements do not establish tenant-mailbox compromise.
N-able says it has emailed partners about their environments and whether action is needed. Partners who did not receive that communication should contact Technical Support. A publicly reposted message describes more specific credential actions, but those details have not been verified against a readable original vendor communication here; obtain your own instructions directly. L4 reflects vendor-confirmed unauthorized access at a hosted email-service provider, with downstream scope still under investigation.
At 00:01 UTC on November 19, N-able reported that it had begun testing some remediation measures while work on others continued. It requires security validation in a controlled environment before bringing back the dashboard, quarantine, logging, mailbox synchronization or API access. Mail flow and filtering continue normally; portal and API access remain disabled during testing. This is remediation progress, not a restoration announcement or a final impact assessment.
At 04:01 UTC on November 19, N-able reported additional platform hardening alongside remediation testing and the continuing investigation. Filtering remains normal and portal/API access remains disabled; this update does not announce restoration or a final impact assessment.
Crime-scene timeline
Nov 16, 2026
N-able initially treats disruption as a service issue
Its later security update says customers were informed about a disruption on this date.
Nov 17, 03:00 UTC
Public incident record starts
Dashboard and supporting-service problems are initially investigated as an operational issue.
Nov 18, 03:05 UTC
N-able confirms a security incident
The vendor identifies unauthorized access to one server, disables UI/API access and says the incident is unrelated to N-central.
Nov 18, 20:18 UTC
N-able confirms partner-specific communications
Mail flow and filtering continue. UI, APIs, quarantine and logging remain offline; N-able asks partners without its email to contact Technical Support.
Nov 19, 00:01 UTC
N-able starts testing remediation measures
Some measures are in testing while others remain in progress. Dashboard, quarantine, logging, mailbox synchronization and API access must pass security validation in a controlled environment before returning online; portal and API access remain disabled.
Nov 19, 04:01 UTC
N-able continues platform hardening alongside remediation testing
Investigation and testing continue while additional security hardening is applied. Mail filtering operates normally; portal and API access remain disabled as a precaution.
Who said what
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.
- N-able public incident 202672PrimaryConfirms server intrusion, distinct N-central scope, continuing mail flow and partner communications.
- N-able public dashboard data for incident 202672PrimaryUnauthenticated JSON used by the public status page; explicitly gives UTC timestamps and the full update history.