Security / News explained
Barracuda ESG flaws connect configuration restore to root access
Barracuda reports exploitation of two linked flaws. The ESG authentication bypass, command-injection conditions and product-specific patches need careful separation.
Barracuda has reported exploitation of vulnerabilities that can combine to give an attacker root access to an Email Security Gateway (ESG). Its advisory was published November 2, 2026; the exploitation update was added November 9. The attacker needs access to the appliance's administrative interface. [1]
CISA added CVE-2026-116606 and CVE-2026-111560 to its Known Exploited Vulnerabilities catalog on November 10, with November 13 remediation dates for the applicable federal requirements. Those dates give the announcement a sharper operational edge. [4]
The two flaws start with different permissions
Mandiant describes CVE-2026-116606 as an ESG authorization bypass: an unauthenticated remote attacker can invoke configuration import or restore using a crafted, compatible backup. That can change the appliance's global configuration. The research disclosure was published November 2, after a report to Barracuda on October 22. [2]
CVE-2026-111560 concerns shell metacharacters in a timezone configuration field. Mandiant says an authenticated administrator can cause operating-system commands to execute as root when that setting is processed. It reported this flaw on October 15 and published the disclosure November 2. [3]
ESG is affected by both vulnerabilities. Barracuda lists ADC, Message Archiver, WAF Control Center, Web Application Firewall and Web Security Gateway as affected by the command flaw only. Its November 5 correction makes clear that the ESG bypass requires reachable administration, not a successful administrator login. [1]
Our interpretation is that configuration restoration is the crucial bridge here. A restore operation changes the assumptions under which the device runs. If it accepts an unauthenticated request, a second weakness in processing the resulting settings can become much more consequential. Treating backup import as a harmless file-transfer feature would miss the security role of the operation.
This also explains why the product distinction matters. An administrator-only command flaw and an unauthenticated path into configuration are different starting positions for an attacker. A summary that assigns the complete ESG chain to every product in the table would give operators the wrong model of their exposure.
Firmware numbers and patch records both matter
Mandiant lists ESG versions before 9.4.0.030 for the import bypass and ESG 9.4.0.27 and earlier for the command flaw. These are the research disclosures' affected-version ranges; use the vendor's current remediation guidance when choosing an update. [2] [3]
For the command flaw, Mandiant also lists ADC 6.4.0 and earlier, WAF 11.0.1 and earlier, WSG 16.1.100.100 and earlier, Message Archiver 5.5.4.0 and earlier, and WAF Control Center 2.2.1 and earlier. [3]
Barracuda specifies ESG patch BNSF-40425 for 9.4.017 and above, or BNSF-40430 below 9.4.017. That dividing line selects a patch; it does not establish that every firmware version above it is fixed. [1]
The vendor calls for current firmware and all security patches. If a patch was not applied automatically, it should be applied manually; appliances far behind may need multiple firmware updates. Barracuda recommends limiting administrative access to trusted internal networks. [1]
For an operations team, the useful question is whether each applicable appliance has the required protection installed. A firmware screenshot and a patch history answer related questions, but they are not interchangeable. The patch identifier is worth preserving alongside the version and the time the check was made.
Exposure and compromise are separate findings
Consider a hypothetical organization with one ESG management interface available through a restricted administration network and another temporarily exposed during maintenance. The product name and firmware could match, while the reachable attack paths differ. That example illustrates why network exposure belongs in the review; it does not describe an incident or establish that either appliance was compromised.
We would prioritize resolving three uncertainties: which product is present, whether the administrative interface was reachable from an untrusted location, and whether the applicable patches are installed. Where exposure or suspicious activity is found, the response should include qualified investigation rather than assuming that applying a patch explains everything that happened earlier.
A management interface is an unusually powerful place to accept instructions. This advisory shows why its reachability, authentication checks and configuration-processing behavior deserve attention together. The immediate work is concrete: establish the device's actual update state and close the documented exposure path, with the vendor's product distinctions intact.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- Pre-Authentication Authorization Bypass and Command Injection Vulnerabilities in Certain Barracuda ProductsBarracuda Networks · Checked Nov 11, 2026
- MNDT-2026-0042: ESG configuration import authorization bypassMandiant · Checked Nov 11, 2026
- MNDT-2026-0041: Barracuda timezone command injectionMandiant · Checked Nov 11, 2026
- Known Exploited Vulnerabilities CatalogCISA · Checked Nov 11, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.