N-able restricts N-central features as new flaws are exploited on 21 servers
N-able is restricting some N-central features and integrations after public disclosure of two flaw sets, 4EverAble2Shell and Agent2Shell. The headline reports 21 infected servers, 19 of them on Hotfix 2.

Key points
- N-able said it is restricting certain N-central features and integrations as an extra precaution.
- The flaws are tracked as 4EverAble2Shell and Agent2Shell and were publicly disclosed.
- The headline reports 21 infected servers, including 19 running Hotfix 2.
- The company warns the restrictions may affect some functionality while remediation is completed.
What happened
N-able said in an update on Thursday that it is taking additional precautions following the public disclosure of a new set of flaws in its N-central remote monitoring and management platform. The flaws are tracked as 4EverAble2Shell and Agent2Shell.
The company stated that it is restricting certain N-central features and integrations. It acknowledged that these measures may affect some functionality, but said the extra caution is warranted while remediation is completed.
Exploitation reported
According to the source headline, attackers have exploited the flaws to infect 21 servers, of which 19 were running Hotfix 2. This suggests that having applied that hotfix did not protect those systems. The excerpt available to us does not give further technical detail, affected version ranges, CVE identifiers or a patch timeline, so we do not speculate on them.
Why it matters
N-central is a management tool that typically holds privileged access across many endpoints. A compromised management server can therefore become a route into every environment it manages. Organisations that run N-central themselves, or whose managed service providers do, should treat this as a supply-chain exposure and follow N-able's own guidance as it is updated.
What to do now
- Identify whether N-central is used internally or by any managed service provider with access to your environment.
- Follow N-able's latest guidance and expect reduced functionality from the restricted features and integrations.
- Do not assume Hotfix 2 is sufficient; check N-central servers for signs of compromise.
- Limit network exposure of N-central servers and review the privileged accounts and integrations connected to them.
- Ask providers in writing about their exposure and response, and escalate through your incident process if indicators are found.
How useful was this story?
0.0 out of 5 · 0 ratings
Our consultants can assess your exposure and map the change to your controls and evidence.
