MAG212 CYBER ORIGINAL ARTICLE

Barracuda CVE-2026-116606 and CVE-2026-111560: From Admin Interface to Root, and the Patch for Each Product

November 5, 2026 · El Mostafa Ouchen

Barracuda ESG Chain: From Admin Interface to Root

Barracuda has patched two flaws that, chained together, let an attacker who can reach an appliance’s admin interface run commands as root. CVE-2026-116606 affects the Email Security Gateway (ESG). CVE-2026-111560 affects six Barracuda products. No exploitation has been reported, but the first fix doesn’t need a patch: take admin interfaces off untrusted networks.

Key facts

ItemDetail
AdvisoryBarracuda, “Pre-Authentication Authorization Bypass and Command Injection”, November 2, 2026
CVE-2026-116606CVSS 4.0 9.3 (CWE-288); ESG before 9.4.0.030; config import accepts a crafted backup (Mandiant MNDT-2026-0042)
CVE-2026-111560CVSS 4.0 8.6 (CWE-78); OS command injection via the timezone setting, runs as root (Mandiant MNDT-2026-0041)
Chained impactAuthorization bypass to root access, per Barracuda
ExploitationNone reported in sources we checked; no KEV listing found
AlertsThaiCERT (Nov 5); Canadian Cyber Centre AV26-1112
Diagram of the Barracuda authorization bypass and command injection chain to root, with patches by product
The chain as Barracuda and Mandiant describe it, and the patch for each product. MAG212 CYBER original diagram.

How the chain works

Mandiant’s advisory for CVE-2026-116606 says an unauthenticated attacker can reach ESG’s configuration-import function and restore a crafted backup archive. Its advisory for CVE-2026-111560 says an administrator-level attacker can inject operating-system commands through the timezone configuration field, and those commands run as root. Barracuda says that, chained, the flaws let an attacker “bypass authorization controls and obtain root access to the device.”

One conflict to know about: Barracuda’s own table says “Administrative access required” for both CVEs and labels both “High”. Mandiant rates the bypass as needing no privileges, and the CVE record rates 9.3 as Critical. In both readings, the attacker has to be able to reach the admin interface.

Affected products and patches

ProductCVE-2026-111560 vulnerable up toPatch
Email Security Gateway9.4.0.27 (and CVE-2026-116606 before 9.4.0.030)BNSF-40425 (firmware 9.4.017 and later) or BNSF-40430 (older)
Load Balancer ADC6.4.0BNADC-16586
Web Application Firewall11.0.1BNADC-16586
Web Security Gateway16.1.100.100BNYF-24789
Message Archiver5.5.4.0BNMA-32468
WAF Control Center2.2.1BNWF-60060

Versions are from the CVE record and Mandiant; the Canadian Cyber Centre lists the same numbers as “prior to”. Version formats differ between sources, so confirm your build with Barracuda Support.

What to do, in order

  1. Restrict admin interfaces to trusted internal management networks. This is Barracuda’s first recommendation.
  2. Confirm the firmware is current, then apply the patch for each product. If automatic patching didn’t apply it, install it manually and turn auto-patching on.
  3. Devices several versions behind may need more than one update; Barracuda says to contact support.
  4. If root access is suspected, preserve evidence with vendor support before rebuilding, then rotate secrets the appliance held.
  5. Verify patch status on every node, standby units included. Confirm the admin UI is refused from untrusted zones and that mail flow, load balancing or archiving works normally.

What to look for

  • Which networks can reach each appliance’s admin UI, tested separately from mail or web traffic.
  • Configuration imports or restores, timezone changes and new administrators that don’t match maintenance records.
  • Unexpected outbound connections or processes on the appliance. Ask Barracuda Support for diagnostics.

Scheduled restores and configuration pushes leave the same traces, so check change records before escalating.

Frequently asked questions

Is the Barracuda chain being exploited?

No source we checked reports exploitation, and we found no CISA KEV listing. That can change quickly for email gateways, so patch now.

Do I need to patch if my admin interface isn’t public?

Yes. Restricting access lowers the risk, but anyone who can reach the interface, including from inside the network, can attempt the chain.

Which ESG patch do I need?

BNSF-40425 for firmware 9.4.017 and later; BNSF-40430 for older firmware.


Sources

Related coverage on MAG212 CYBER