An attacker can change a Barracuda Email Security Gateway’s global configuration by restoring a crafted backup without logging in. CISA added the authentication bypass, CVE-2026-116606, to its Known Exploited Vulnerabilities catalog on November 10. For teams running ESG appliances, that makes an unexpected configuration restore a compromise lead as well as a patching problem.
CISA sets November 13 as the remediation due date in its catalog and calls for vendor-directed mitigations and forensic triage under its federal guidance. The date is a federal deadline; operators outside that mandate still have an actively exploited gateway flaw to address.
A backup enters without login
The bypass reaches the appliance’s configuration-import function through an alternate authentication path. CISA describes an unauthenticated remote attacker able to “restore a crafted, compatible backup archive,” changing global configuration. A backup restore changes global gateway settings the appliance will use after the import.
Mandiant’s CVE record marks Barracuda ESG releases earlier than 9.4.0.030 affected. Check the installed build on each ESG appliance, including standby or less-used units. Restrict access to administrative services from trusted admin hosts while arranging the vendor-directed update; keep the mail path available. This network restriction cuts reachability to the administrative surface, while the installed build determines whether the recorded flaw remains present.
Timezone settings can reach root
CISA says the bypass can be chained with CVE-2026-111560. Mandiant describes that second flaw as command injection in a timezone configuration field: when a crafted value is later processed, OS commands execute with root privileges. On ESG, its record marks versions through 9.4.0.27 affected. The command-injection record describes an authenticated administrator as its direct attacker; the backup-restore bypass supplies a route to modify global settings without those credentials. A restored backup that alters timezone settings therefore deserves investigation as a possible path to root execution.
The command-injection record also lists other Barracuda appliance families. Their affected versions differ from ESG’s; apply each product’s own vendor guidance rather than using the ESG build number across the fleet.
Examine restores, then update ESG
Inventory ESG versions and internet exposure first. Follow Barracuda’s advisory linked from CISA’s record for the applicable update or mitigation. Mandiant’s affected-version boundary for the bypass is below 9.4.0.030; verify the actual installed build after any update, including on standby appliances.
Preserve the current configuration and available appliance or centralized syslog before making changes if compromise is suspected. Look for configuration imports or restores you did not authorize, unexpected global settings, and changes to the timezone field. Compare the timing with administrative access and network connections to the appliance. If local logging is thin, use upstream firewall and centralized records to reconstruct access; a normal-looking current configuration alone is a weak history of what was restored.
Test from a non-admin network that administrative access is blocked while mail delivery continues. Then confirm each ESG reports 9.4.0.030 or a vendor-recommended later build. If a restore or timezone change is unexplained, keep the evidence and involve the incident-response team before treating the version check as the end of the investigation.