Barracuda Timezone Flaw Gives Appliance Admins Root Command Access
CISA lists active exploitation across Barracuda appliances. An email-gateway authentication bypass can be chained with the timezone flaw; isolate management access and check builds.

Barracuda appliance administrators face a root-level command-injection flaw that CISA marked as exploited on November 10. The entry covers Barracuda email, web, archiving and application-delivery products. A crafted timezone setting reaches root execution when the appliance later processes it. CISA also says the flaw can be chained with a separate authentication bypass in the Email Security Gateway, or ESG.
For ESG owners, check who can reach the management interface. The command-injection flaw, CVE-2026-111560, requires administrator privileges on its own. The linked ESG flaw, CVE-2026-116606, lets an unauthenticated remote actor change global configuration on affected gateways. CISA has set November 13 as its action date for the exploited command-injection entry. Treat the date as an immediate scheduling cue for the appliances you operate.
Timezone processing reaches root privileges
The CVE record assigned by Mandiant describes improper handling of shell metacharacters in a shared Barracuda timezone configuration field. A signed-in administrator can supply a crafted value; when the appliance processes that value afterward, operating-system commands run with root privileges. CISA describes the execution point as occurring “when the crafted timezone value is subsequently processed.” When investigating a timezone edit, look for root-level activity after the change as well as at the time it was saved.
An ESG handles mail; WAF and WSG products handle web traffic; the archiver holds mail records; ADC products deliver applications. Root execution on any such appliance places its local operating system under the attacker’s control, with the data and traffic available to that device at risk. CISA lists the flaw as exploited; review prior configuration changes as you apply vendor-directed mitigations.
Email gateways have another entry
The second Mandiant-assigned CVE record describes an ESG authentication bypass in releases earlier than 9.4.0.030. It permits an unauthenticated remote actor to reach a configuration-import function and restore a crafted compatible backup, altering global configuration. This is the route CISA says can be paired with the timezone injection. The two records describe distinct access conditions: the timezone flaw starts with administrator control; the ESG import flaw provides a way to alter configuration without a normal administrator sign-in.
Investigate unexplained configuration restores and timezone edits on an exposed ESG as potential compromise signals. Treat an unexplained change as an incident and assess appliance integrity even if the installed build is current. Keep the investigation tied to the affected device and its management reachability. Compare the appliance configuration history with approved changes, and request product-specific forensic indicators from Barracuda for deeper hunting.
Compare builds across product families
The Mandiant-assigned CVE-2026-111560 record gives these affected ranges for the administrator-to-root issue:
| Product | Affected releases through |
|---|---|
| Email Security Gateway (ESG) | 9.4.0.27 |
| Load Balancer Application Delivery Controller (ADC) | 6.4.0 |
| Web Application Firewall (WAF) | 11.0.1 |
| Web Security Gateway (WSG) | 16.1.100.100 |
| Message Archiver (BMA) | 5.5.4.0 |
| WAF Control Center (WCC) | 2.2.1 |
CISA separately names Load Balancer alongside ADC in its seven-family description. If you operate a Load Balancer identified under that name, get its applicable release mapping from Barracuda before clearing it. For ESG, check both records: the authentication-bypass range is earlier than 9.4.0.030, while the command-injection record lists releases through 9.4.0.27. The different endpoints belong to different flaws. The CVE ranges are exposure bounds; use Barracuda’s security advisory for the current supported update and any deployment-specific mitigation.
Restrict management and update appliances
Start with an inventory of the named Barracuda products and their installed builds. Record which management interfaces can be reached from the internet, user networks and administrative jump hosts. Restrict administrative access to the hosts that need it, especially on ESG systems where the import bypass changes the access condition. Apply Barracuda’s current mitigation instructions and compare the installed build with the relevant product and CVE range afterward. CISA calls for vendor-directed mitigation and forensic triage, and its November 13 action date makes the ESG and other affected appliances an urgent change-window decision.
For ESGs, compare timezone and global-configuration changes against approved administrator work. Examine configuration-restore activity and investigate an unexplained change as a possible compromise, particularly where management was exposed. An installed update addresses exposure going forward; root-level activity calls for separate incident investigation. After suspected root-level activity, use appliance-specific forensic evidence and Barracuda recovery guidance to decide when the gateway can return to service.
A practical verification is to repeat the inventory after the maintenance window: each affected appliance should have the approved vendor mitigation applied, its installed build recorded, and its management interface reachable only from the intended administrator hosts. Review any unexplained ESG configuration restore before treating that gateway as recovered.