Barracuda ESG Root Chain Under Attack: Patch, Lock Down the Admin UI, and Check Your Config
CVE-2026-116606 and CVE-2026-111560 chain to root on Barracuda email gateways and WAFs. How to patch, close the admin UI, and check for compromise.
- Author
- Ackatec
- Published
- Reading time
- 5 min read
- Vulnerability management
- Email security
- Incident response
- Penetration testing
- CISA KEV
Two Barracuda vulnerabilities that chain to root access are now being exploited. On November 9, 2026, Barracuda updated its security advisory (opens in a new tab) to say it had identified exploitation activity affecting a small number of organizations. A day later, CISA added both flaws (opens in a new tab) to its Known Exploited Vulnerabilities (KEV) catalog with a November 13 due date for federal agencies and a forensic triage requirement.
The short answer: if you run a Barracuda Email Security Gateway (ESG), Web Application Firewall, Load Balancer ADC, Message Archiver, WAF Control Center, or Web Security Gateway, confirm today that the administrative interface is not reachable from the internet, apply the vendor patch, and verify the firmware version. For ESG appliances, also review the configuration for changes you did not make, because the first flaw lets an attacker rewrite it without logging in.
What are CVE-2026-116606 and CVE-2026-111560?
They are two separate bugs that become far more dangerous together.
- CVE-2026-116606 is a pre-authentication authorization bypass in the ESG, rated CVSS 9.3. According to Mandiant's disclosure (opens in a new tab), an unauthenticated remote attacker can invoke a configuration-import function and restore a crafted backup archive, which modifies the appliance's global configuration.
- CVE-2026-111560 is an OS command injection rated CVSS 8.6. Mandiant's write-up (opens in a new tab) explains that shell metacharacters in the timezone configuration field let an authenticated administrator run commands as root when that value is later processed. It affects the ESG, ADC, Message Archiver, WAF, WAF Control Center, and Web Security Gateway.
Barracuda states that, used in combination, the two flaws could allow an attacker to bypass authorization controls and obtain root access to the device. On November 5, Barracuda changed the advisory to say that CVE-2026-116606 does not require authentication; it requires only that the attacker can reach the Admin UI.
Why does a KEV listing matter outside government?
The KEV deadline binds federal civilian agencies, but the signal applies to everyone: CISA has evidence of active exploitation. Both entries are flagged "Forensic triage required" in the KEV catalog (opens in a new tab), meaning agencies must remediate within three days and also check whether the device was already compromised. That two-part expectation is a sound standard for any organization. For background on how that triage requirement works, see our post on BOD 26-04.
Which Barracuda products and versions need patching?
Barracuda lists a patch for each affected product:
- Email Security Gateway (ESG): affected by both CVEs. Patch BNSF-40425 for firmware 9.4.017 and later, or BNSF-40430 for earlier firmware.
- Load Balancer ADC: affected by CVE-2026-111560. Patch BNADC-16586.
- Web Application Firewall (WAF): affected by CVE-2026-111560. Patch BNADC-16586.
- Message Archiver (BMA): affected by CVE-2026-111560. Patch BNMA-32468.
- WAF Control Center (WCC): affected by CVE-2026-111560. Patch BNWF-60060.
- Web Security Gateway (WSG): affected by CVE-2026-111560. Patch BNYF-24789.
For the ESG, Barracuda's Campus instructions (opens in a new tab) say to upgrade and then confirm the appliance reports firmware 9.4.0.029 or later. Appliances below 9.1 must update in two steps. Mandiant's disclosure describes CVE-2026-116606 as affecting versions earlier than 9.4.0.030, so if a newer release than 9.4.0.029 is offered, take it. Barracuda also recommends turning automatic patching back on for any device where it was disabled.
How do you respond in the next 72 hours?
Treat this as a short incident response, not a routine patch ticket.
1. Find every affected appliance
List physical, virtual, and cloud instances of all six products, including lab, disaster recovery, and acquired-company units that may sit outside your asset inventory. Record the firmware version and who owns each device.
2. Close the admin interface from the internet
Barracuda notes that organizations whose administrative interfaces are not publicly accessible are less exposed, and recommends restricting access to trusted internal networks. Test this from outside your network rather than trusting a firewall rule on paper. An exposed admin page found this way is exactly the kind of issue an external penetration test is meant to surface before an attacker does.
3. Preserve evidence before you change anything
If an ESG admin interface was reachable from the internet at any point before you patched, save the current configuration and available logs before patching or rebooting. A patch closes the door. It does not tell you whether someone already walked through it, and a reboot can destroy useful evidence.
4. Patch and verify
Apply the patch or firmware update, then confirm the installed version on the device itself. Repeat updates until the device reports the fixed version.
How can you tell whether an ESG was compromised?
As of November 11, Barracuda's advisory lists no indicators of compromise, so compare the device against what it should look like. Because CVE-2026-116606 restores a crafted backup into the global configuration, focus on settings an attacker could use for persistence or mail access:
- Administrator accounts, roles, and the IP ranges allowed to reach the admin interface.
- Mail routing, destination servers, relay rules, and any forwarding you did not configure.
- Allow lists and policy exceptions that would let malicious mail bypass filtering.
- Stored credentials for directory lookups, SMTP authentication, or integrations. Rotate them if the device may have been exposed.
- The timezone setting itself, which is the field CVE-2026-111560 abuses. A value containing shell characters such as semicolons, pipes, or backticks instead of a plain timezone name is a red flag.
Also review outbound connections from the appliance for destinations you do not recognize.
Should you rebuild or replace the appliance?
If you find unexplained changes, assume root-level compromise and escalate to incident response rather than reverting settings by hand. There is precedent. After the 2023 ESG zero-day CVE-2023-2868, Barracuda recommended that impacted customers replace (opens in a new tab) compromised appliances instead of relying on patches alone. Decide in advance who makes that call and who performs the forensics.
What should security leaders take from this?
Email gateways and WAFs sit at the edge, see sensitive traffic, and can hold directory credentials. That makes them attractive targets, and their management interfaces should never face the internet. Three questions are worth answering this week:
- Do we know every internet-reachable management interface we own, across all vendors?
- Can we capture evidence from an edge appliance before patching it, and who does the forensics?
- Who decides whether a device is rebuilt or replaced, and how fast?
If any answer is unclear, a security assessment can find the material gaps in how you track and patch edge devices, and an incident readiness tabletop built around a compromised email gateway can turn the steps above into practiced roles. Following them reduces risk but does not guarantee that a device was not already compromised. Talk with Ackatec about where to start.
