Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Screenshot of the N-able Uptime page showing an active incident, ID 202672, started Nov. 17, 2026 at 03:00 UTC with severity Major Outage, titled Security Incident, Mail Assure and SpamExperts Hosted Cloud, all regions, and listing six impacted services.
Image: N-able (fair use). The N-able Uptime page entry for the Mail Assure and SpamExperts incident, as of Thursday morning, Nov. 19.

Response

N-able Says an Intruder Reached a Server Behind Its Mail Assure and SpamExperts Email Filtering, Hours After Blaming the Outage on Configuration, and Quarantine and Logs Have Been Dark Since Tuesday

Mail is still being filtered, but customers and the managed service providers who resell the service cannot release quarantined messages, review logs or change settings in any region. N-able says it has no evidence that customer data or mailboxes were accessed, and has not said how the intruder got in.

Noah Park, ResponseNew York5 min read

NEW YORK - N-able, whose software many managed service providers use to run their clients' networks, said that an unauthorized party gained access to a server in the hosted cloud behind its Mail Assure and SpamExperts email filtering services, an incident it had described the day before as a problem with platform configuration.

The company disclosed the intrusion on its public status page at 03:05 UTC on Wednesday. As of its latest update, at 08:00 UTC on Thursday, the management portal, APIs, quarantine, logging and mailbox synchronization for both services remained offline in the Americas, Asia-Pacific and Europe, while inbound and outbound mail filtering continued to run.

"We are aware of unauthorized access to one of the servers in the Mail Assure and SpamExperts Hosted Cloud," N-able wrote. "The investigation is ongoing, but at this time we do not have evidence that customer data was compromised, including access to tenants' mailboxes."

From configuration problem to security incident

The status page entry opened at 03:00 UTC on Tuesday, Nov. 17. Three hours later N-able said dashboard access was affected and mail filtering was working. At 13:33 UTC that day, it said it had found the root cause: "a combination of platform configuration and service dependencies," which required "rebuilding affected infrastructure and updating several platform components."

Screenshot of the N-able Uptime timeline entry from Nov. 17, 2026 at 13:33 UTC saying the issue was traced to a combination of platform configuration and service dependencies and that remediation required rebuilding affected infrastructure.
Image: N-able (fair use).N-able's original explanation of the outage, Nov. 17.

About 14 hours later the company revised that account. "Our earlier update said the disruption came from platform configuration and service dependencies and we believed we had remediated the issue," it wrote. "As we continued our investigation, we determined that the disruption was caused by a security incident." It said it had taken steps to mitigate the threat, was hardening its services, and had "proactively disabled UI and API access" while the investigation continued. It also said the incident was unrelated to the attacks on its N-central remote management product earlier this month.

Screenshot of the N-able Uptime timeline entry from Nov. 18, 2026 at 03:05 UTC titled Mail Assure and SpamExperts Hosted Cloud Security Incident, describing unauthorized access to one server and saying the incident is unrelated to N-central.
Image: N-able (fair use).The Nov. 18 update that reclassified the outage as a security incident.

N-able has not said how the intruder reached the server, what the server did, when the access began, or whether any credentials, API keys or configuration stored in the environment were exposed. Its Wednesday evening update said it had emailed Mail Assure and SpamExperts partners "with information relevant to their environment and whether action is required or not," and asked anyone who had not received that message to contact technical support.

What the outage takes away from defenders

Filtering still runs, so spam and malware screening has not stopped. What has stopped is everything an analyst would use to work an email case through these products. N-able said on Wednesday that until services return, customers "may be unable to sign in to the control panel, view or release quarantined messages, review logs, or make configuration changes such as adding or removing domains."

For a security team, that means investigations that depend on the filter's own records, such as tracing whether a reported phishing message was caught, released or delivered, have to rely on other sources, like the message trace in the mail platform behind the filter, until the portal is back. Messages held in quarantine since Tuesday cannot be reviewed or released, and any rule change made in response to a new campaign has to wait.

The restoration will not be quick. N-able said early Thursday that before any service returns, it "must pass security validation in a controlled environment," covering the dashboard, quarantine, logging, mailbox synchronization and API access, and that the work was continuing around the clock.

A month of incidents

The disclosure comes during a difficult stretch for the company. N-able has been patching N-central since Nov. 9, when it began responding to what it calls zero-day vulnerabilities that were not responsibly disclosed, and released a third hotfix, 2026.4 HF3, that it said hardens authentication and agent communications and removes the legacy API. In a Nov. 12 update, it said it had identified indicators of compromise and was working with the specific customers affected.

Screenshot of the N-able Uptime timeline entry from Nov. 19, 2026 at 00:06 UTC on CVE-2026-114938, saying hosted N-central is not affected and that on-premises customers on Intel Ice Lake or AMD Zen 4 and later processors should open a support case for a remediation script.
Image: N-able (fair use).N-able's Java4Shell guidance for N-central, posted Nov. 19.

It is also handling Java4Shell, the Java runtime flaw disclosed on Tuesday. N-able said early Thursday that hosted N-central is not affected, that only a small portion of on-premises N-central servers meet the hardware conditions, and that customers whose servers run on Intel Ice Lake or AMD Zen 4 and later processors should open a support case so N-able staff can run a remediation script, with brief downtime. It corrected an earlier note that had said customers could run the script themselves.

About the Author

Noah Park

Noah Park covers incident response, containment, and blue-team operations for SOCtember from New York.

Related stories

Response desk