Yes — N-able confirmed a security incident affecting Mail Assure and SpamExperts Hosted Cloud (the hosted email-filtering stack many managed service providers sell to small offices, law firms, and CPA practices). N-able’s uptime event 202672 states that mail flow and filtering continue to operate, while the dashboard, API, quarantine, logging, and mailbox synchronization remain offline while restoration and security validation continue.
On November 18, 2026, N-able’s timeline says the disruption was caused by a security incident (not only platform configuration). The company reported unauthorized access to one of the servers in the environment, no evidence that customer data was compromised, including access to tenants’ mailboxes, and that the incident is unrelated to the N-central incident. SecurityWeek (November 20, 2026) cites N-able’s statement that the incident was isolated to a single web server and that an unauthorized party may have been able to access certain credentials stored on the platform. That credential language is from N-able’s statement to SecurityWeek — not a confirmed mailbox compromise.
This post is a practical checklist for SMBs, law firms, and accounting practices that rely on an MSP for hosted spam filtering, not a vendor product review.

Snapshot
| Field | Detail |
|---|---|
| Product lines | Mail Assure · SpamExperts Hosted Cloud (also branded SpamExperts) |
| Regions | Americas, APAC, Europe (per uptime event) |
| Mail filtering | Operating — inbound and outbound filtering per N-able updates through Nov 20, 2026 |
| Portal / API / quarantine | Offline as a precaution while remediation continues |
| Customer mailboxes | N-able: no evidence tenant mailboxes were accessed (uptime Nov 18 update) |
| Credentials | SecurityWeek: unauthorized party on one web server may have accessed certain credentials stored on the platform |
| N-able actions cited | Containment, internal credential rotation, customer API token revocation, OAuth invalidation, local user password resets (SecurityWeek) |
| Distinction | N-able states this is unrelated to the recent N-central incident |
Timeline (UTC, from N-able uptime)
| When | What N-able published |
|---|---|
| Nov 17, 2026 ~03:00 | Incident opened; investigation underway |
| Nov 17, 2026 06:10 | Dashboard access affected; mail filtering remains operational |
| Nov 18, 2026 | Confirmed security incident; mail flow and filtering still operating; portal/API/quarantine remain offline |
| Nov 19–20, 2026 | Continued restoration, remediation testing, and security hardening; portal/API still disabled |
What small law and CPA firms should do this week
1. Rotate credentials your MSP or you control for the filter.
N-able told SecurityWeek it revoked customer API tokens, invalidated OAuth tokens, and reset local user passwords. If your provider has not confirmed those steps for your tenant, ask explicitly. Change any password you reused between the filter console and Microsoft 365, Google Workspace, or client portals.
2. You cannot manage quarantine in the portal — assume risk shifts to users.
While quarantine is unreachable, more unwanted mail may reach inboxes or users may miss false positives. Brief staff: do not release messages or click quarantine links from unexpected email pretending to be “Mail Assure” or your MSP.
3. Review allowlists, blocklists, and forwarding rules when access returns.
Attackers who obtain filter credentials sometimes add allowlist entries or forwarding rules. When the portal is back, compare rules against a known-good export or have the MSP show a screen share audit.
4. Watch for phishing that cites the incident.
Expect messages claiming “reset your spam filter password” or “download quarantined wire instructions.” Use your MSP’s ticket system or a published status page — not reply links in mail.
5. Confirm SPF, DKIM, and DMARC on your domain still pass.
The filter outage does not excuse weak authentication on your brand. Weak DMARC makes fake CPA or law-firm mail easier while staff are distracted by vendor status pages.
| Check | Action |
|---|---|
| DMARC | Policy at p=reject or p=quarantine with alignment on payroll and client-facing senders |
| DKIM | Signing still active on M365/Google after any connector changes |
| SPF | No surprise includes; avoid -all conflicts with the filter path your MSP documents |
| MTA-STS / TLS | Enforced where your mail stack supports it |
MSP and client communication
N-able’s November 18 uptime note says it emailed Mail Assure and SpamExperts Hosted Cloud partners with environment-specific guidance. If you are an end client, your MSP should relay whether you must act. If you have not heard from the MSP, open a ticket — do not infer “no action” from a news headline alone.
Related reading
- Apache Axis / Confluence / N-central CVE roundup (Nov 2026) — separate N-able N-central context
- Barracuda cloud intrusion — vendor key hygiene
- Texas CPA firm OAG breach tracker
- Law firm breach tracker
- MFA support directory
- Breach monitoring resources guide
Check your domain free at audit.emailmenow.com, add Domain Watch ($29/mo) for weekly mail-authentication drift monitoring, add Cybersquat Domain Monitoring ($49/mo add-on) if lookalike domains are part of your firm’s plan, or unlock the Full Audit Report ($99) via automated reports and monitoring. We did not run new domain score audits for this advisory.
Sources: N-able uptime event 202672 · SecurityWeek — N-able cyberattack disruption (Nov 20, 2026)