MONDAY, NOVEMBER 16, 2026 Tech news, minus the noise.
N News Cast
LATEST
Cybersecurity

Hackers Are Exploiting N-able's N-central Zero-Days Right Now. Patch Immediately

A researcher disclosed more than 30 zero-days in N-able's N-central remote management platform on November 8, and attackers were exploiting them within hours. Hotfixes are out, but patched servers were hit too.

Hackers Are Exploiting N-able's N-central Zero-Days Right Now. Patch Immediately
Source: Lapalmauz, Wikimedia Commons (CC BY-SA 4.0)

Thirty Zero-Days, Published All at Once

Security researcher Sean Bales publicly disclosed more than 30 alleged zero-day vulnerabilities in N-able's N-central platform late on November 8, publishing proof-of-concept exploits in a GitHub repository called Able2Shell. Bales confirmed the discovery was AI-assisted, which is a detail worth sitting with: the same AI tools that help defenders find bugs are now helping researchers find them at a scale and speed that manual review cannot match.

N-central is remote monitoring and management software. Managed service providers use it to watch over their clients' computers and servers, push updates, and fix problems remotely. That is what makes this disclosure so serious. Compromise one N-central server and you potentially get access to every organization that server manages.

N-able's response was drastic and fast. On November 9, the company took all hosted N-central environments offline across the Americas, Europe, and Asia-Pacific, and told on-premises customers to shut their servers down. It released hotfixes, versions 2026.4 HF1 and HF2, on November 11, covering the most critical flaws, including CVE-2026-125883, an XML external entity flaw, and CVE-2026-125878, an OGNL injection flaw.

Attackers Moved Within Hours

Disclosure on a Sunday, exploitation within hours. Security firms reported active exploitation almost immediately. Attackers chained a critical Apache Axis flaw, CVE-2026-90436, rated 9.8 out of 10, with an N-central privilege escalation to gain root access and install an XMRig cryptominer on 21 servers across the US, South Africa, Canada, the UK, Germany, France, and Sweden.

Here is the part that should worry every N-central administrator: 19 of those 21 servers were running Hotfix 2. The patch covered the most critical flaws, but the attack chain used a different combination, and the hotfix did not stop it. N-able has since released further guidance, but the incident is a reminder that patching is necessary and not sufficient. If your server was exposed during the window, assume it needs checking, not just updating.

The cryptominer is almost the good news. Attackers who get root on an MSP management server could do far worse than mine cryptocurrency. They could push malicious updates to every managed endpoint, steal credentials, or deploy ransomware downstream. So far the observed activity is mining, but the access the attackers gained would allow much more.

The Same Week, the Same Pattern

N-central was not the only remote management tool abused this week. Attackers gained unauthorized access to cloud-hosted ScreenConnect environments and used the platform's Run Command feature to install rogue remote-access clients, compromising at least 288 endpoints across 48 organizations within 90 minutes. A third of them fell in the first 10 minutes.

The pattern is the same in both cases. Attackers are not breaking into each victim one by one. They are compromising the tools that manage many victims at once, then letting the tool do the distribution. It is efficient, it is fast, and it is very hard to defend against from the victim's side, because the attack arrives through software you trust.

The week also brought confirmed breaches at TSMC and Maersk, both through third-party or legacy systems, and Europol's Operation Endgame seized 235 servers and 257 domains across nine countries. Our October breach wave roundup showed the same shape a month ago: the breaches that matter now live in the supply chain, not the front door.

What to Do If You Run N-central

First, apply every hotfix N-able has released, and check for new ones daily until the company says the incident is closed. The hotfix that covers the disclosed flaws is the floor, not the ceiling.

Second, check for compromise. Look for unexpected processes, especially XMRig or other miners, unexpected scheduled tasks, and new user accounts. N-able has published indicators of compromise, and they are worth checking against your logs even if your server looks clean.

Third, rotate credentials. Any credential that touched the N-central server during the exposure window should be treated as potentially compromised, including service accounts and API keys. Our breach exposure guide covers how to check whether your own accounts appear in known breaches, and our first hour guide covers the immediate steps after you learn your data was exposed.

Fourth, review what your RMM tool can reach. N-central, ScreenConnect, and similar tools have enormous privilege by design. Limit which systems they can touch, segment your network so a compromised management server cannot reach everything, and make sure the management server itself is patched and monitored like the critical asset it is.

The Bigger Lesson

AI-assisted vulnerability research is here, and it is going to make weeks like this one more common. A researcher with AI help found more than 30 flaws in one platform in a single disclosure. Attackers with the same tools will find the next batch just as fast. The window between disclosure and exploitation is now measured in hours, not weeks.

That changes the math for every organization running management software. Patching fast is no longer a best practice. It is the minimum. And assuming your vendor's hotfix covers everything is a mistake the N-central incident just demonstrated in public. Check, rotate, and verify, even after you patch.

AS
News Cast Editorial Team

We cover AI, gadgets, startups and security — original reporting and explainers, written by humans, for humans. Got a tip? Reach us via the contact page.