Zarro Technology · Security briefing

Today’s briefing focuses on two material developments affecting email security and remote management. Barracuda has confirmed exploitation, while newly disclosed N-central vulnerabilities have prompted emergency service restrictions. Older advisories without a verified change are omitted.

1. Barracuda confirms exploitation of appliance vulnerabilities (Critical)

CVE-2026-116606 (9.3), CVE-2026-111560 (8.6)

Impact

In an update dated 9 November, Barracuda confirmed exploitation affecting a small number of organisations. On Email Security Gateway (ESG), an unauthenticated authorisation bypass can be chained with command injection to obtain root access. Attackers must be able to reach the administrative interface. This is a material escalation from our earlier patch coverage.

Checks and IoCs

Check administrative-interface exposure and verify security-patch installation, rather than relying on the firmware number alone. Review unexpected configuration restores, administrator activity and configuration changes; these are investigation leads, not confirmed campaign IoCs. The vendor update does not publish campaign-specific indicators.

Remediation

Install current firmware and all applicable patches. ESG requires BNSF-40425 on 9.4.017+ or BNSF-40430 on older builds. For command injection on other products, verify BNADC-16586 (ADC/WAF), BNMA-32468 (Message Archiver), BNWF-60060 (WAF Control Center) or BNYF-24789 (Web Security Gateway). The unauthenticated bypass is ESG-specific. Restrict management access to trusted networks. If suspicious activity is found, preserve logs and contact Barracuda Support; patching alone does not establish that a device is clean.

Sources: Barracuda advisory — exploitation update, 9 November · Canadian Cyber Centre — updated 9 November

2. N-central emergency: keep on-premises servers offline pending vendor guidance (Critical)

Impact

On 9 November, N-able took hosted N-central environments offline following disclosure of critical vulnerabilities. Huntress is investigating the published Able2Shell exploit chains, which allege code execution and privilege escalation. N-able reported no observed active exploitation in the incident notice reproduced by Huntress. No definitive affected-version matrix or verified fixed release is available in the sources reviewed; do not assume a recent build is protected. No CVE identifiers are listed for these newly disclosed issues.

Checks and IoCs

Huntress recommends reviewing login and authentication activity from 8 November onwards. Investigate unexpected administrator accounts, remote sessions and deployed scripts, including activity on managed endpoints. These are behavioural checks, not proof of compromise or campaign-specific IoCs.

Remediation

Follow the emergency guidance: take on-premises N-central servers offline and keep them offline until N-able confirms safe restoration. Hosted customers should follow the vendor incident page for service updates. Obtain the approved hotfix and restoration instructions through N-able Support; no fixed version is asserted here. Preserve audit evidence and involve incident responders if unauthorised activity is identified.

Sources: Huntress — active investigation and customer checks · N-able — live incident and restoration guidance

Zarro Technology