Linux Vulnerability – Important Update
For additional details, please also see this post from our Nightscope Threat Research tream.
Update: November 3, 2026 10 am ET
We are continuing to assess our products and environments for potential exposure to the recently disclosed Linux vulnerability. At this time, we have not seen any active exploits in any customer environments and are prioritizing our work to apply patches as soon as they are available from the vendor.
We will keep this blog updated with the latest information.
Current product status:
- Adlumin – Cloud services patch applied
- Cove – Mitigation applied; awaiting vendor patch
- N-central – Hosted environments patched; N-central 2026.4 HF1 released for on-premises: N-central 2026.4 HF1 Release Notes | N-able Status
- N-sight – Patch applied
- Mail Assure – Patch applied
- SpamExperts – Patch applied to hosted environments; local cloud customers need to reboot. (See instructions below.)
- Passportal – Awaiting vendor patch
- TakeControl – Patch applied
Update: November 2, 2026 10 am ET
We are continuing to assess our products and environments for potential exposure to the recently disclosed Linux vulnerability. At this time, we have not seen any active exploits in any customer environments and are prioritizing our work to apply patches as soon as they are available from the vendor.
We will keep this blog updated with the latest information.
Current product status:
- Adlumin – Cloud services patch applied
- Cove – Mitigation applied; awaiting vendor patch
- N-central – Vendor patch received; update pending
- N-sight – Vendor patch received; update pending
- Mail Assure – Patch applied
- SpamExperts – Patch applied to hosted environments; local cloud customers need to reboot. (See instructions below.)
- Passportal – Awaiting vendor patch
- TakeControl – Patch applied
Update: October 31, 2026 11:30 am ET
We are continuing to assess our products and environments for potential exposure to the recently disclosed Linux vulnerability. At this time, we have not seen any active exploits in any customer environments and are prioritizing our work to apply patches as soon as they are available from the vendor.
We will keep this blog updated with the latest information.
Current product status:
- Adlumin – Not impacted
- Cove – Mitigation applied; awaiting vendor patch
- N-central – Awaiting vendor patch
- N-sight – Awaiting vendor patch
- Mail Assure – Patch applied
- SpamExperts – Patch applied to hosted environments; local cloud customers need to reboot. (See instructions below.)
- Passportal – Awaiting vendor patch
- TakeControl – Patching in progress
Action required for SpamExperts Local Cloud customers
Please reboot each SpamExperts Local Cloud server as soon as possible. The updated kernel takes effect only after a reboot. Until each server is restarted, it remains on the vulnerable kernel.
Please complete these steps as soon as possible to ensure your infrastructure is secure.
- Confirm the update is present on each Local Cloud server:
dpkg -l | grep ii | grep linux-image | grep 6.1.190 - Reboot each server one at a time so your cluster continues filtering mail during the process.
- After each reboot, confirm the server is running kernel version 6.1.190 (
uname -v) and has rejoined the cluster before moving to the next server.
Original post
N-able is aware of CVE-2026-98432, a recently disclosed vulnerability affecting certain versions of the Linux kernel. We have been assessing our products and environments for potential exposure and are actively applying applicable security updates as they become available from our operating system vendors.
Systems supporting Take Control and Mail Assure are currently being patched. For Cove, N-central, N-sight, Passportal, Adlumin, and other potentially impacted products, we are awaiting applicable operating system vendor patches and will deploy them once available.
For SpamExperts Local Cloud, N-able has released an updated kernel package. Customers must reboot their servers for the updated kernel to take effect. Until each server is restarted, it will continue to run the previous kernel. Customers should reboot servers one at a time and verify that each server has successfully rejoined the cluster before proceeding to the next.
At this time, we have no evidence that this vulnerability has been exploited in N-able-hosted environments. We will continue monitoring vendor guidance, evaluating our products and infrastructure, and taking appropriate action as additional updates become available.
Customers with questions or who need assistance completing the recommended actions should contact N-able Support.
Please follow this blog for updates.
© N‑able Solutions ULC e N‑able Technologies Ltd. Todos os direitos reservados.
Este documento é fornecido apenas para fins informativos e não deve servir de base para aconselhamento jurídico. A N‑able não oferece nenhuma garantia, expressa ou implícita, nem assume qualquer responsabilidade legal ou responsabilidade pela precisão, integralidade ou utilidade de qualquer informação nele contido.
As marcas N-ABLE, N-CENTRAL e outras marcas registradas e logotipos N‑able são de propriedade exclusiva da N‑able Solutions ULC e da N‑able Technologies Ltd e podem ser marcas legais comuns, registradas ou de registro pendente com o Escritório de Marcas e Patentes dos EUA e com outros países. Todas as outras marcas comerciais mencionadas neste documento são usadas apenas para fins de identificação e são marcas comerciais (e poderão ser marcas registradas) de suas respectivas empresas.