Barracuda Patches a Pre-Auth Root Chain in Email Security Gateway — and watchTowr Just Demonstrated It End to End

Barracuda Patches a Pre-Auth Root Chain in Email Security Gateway — and watchTowr Just Demonstrated It End to End

Barracuda Patches a Pre-Auth Root Chain in Email Security Gateway — and watchTowr Just Demonstrated It End to End

Barracuda has patched two vulnerabilities in its appliances that chain into something no security vendor wants on its label: root access with no login required. The flaws, assigned by Mandiant, are CVE-2026-116606 (CVSS 9.3), a pre-authentication authorization bypass affecting the Email Security Gateway, and CVE-2026-111560 (CVSS 8.6), a command injection that reaches six products — the Email Security Gateway, Load Balancer Application Delivery Controller, Message Archiver, WAF Control Center, Web Application Firewall, and Web Security Gateway. Barracuda released patches on Monday, and on Thursday researchers at watchTowr published a technical walkthrough showing the full chain working on the Email Security Gateway, where the combination turns an unauthenticated network position into arbitrary commands running as root.

The chain is a two-step classic. First, the authorization bypass: a failed password change on the ESG returns the attacker a low-privilege role instead of stopping the request, which leaves a backup-restore function reachable by someone who never logged in. Second, the injection: the restored backup includes a timezone value that the appliance later passes to a shell with root privileges. Barracuda guards configuration backups with a checksum, but the secret used to compute it is built into the appliance's code — so an attacker can forge a valid checksum and simply upload a poisoned backup. watchTowr demonstrated the chain by writing a file to the appliance as root, released a detection tool that checks whether an appliance is vulnerable, but has not published an exploit.

On the other five products, the command injection alone still requires an administrator account — it is the ESG's bypass that removes the authentication requirement. Barracuda's own framing is blunt: "Successful exploitation requires an attacker to have access to the administrative interface of an affected product," and organizations that do not expose administrative interfaces to the internet are less vulnerable. The Email Security Gateway is fixed in 9.4.0.030 and later, with per-product fixed firmware in the advisory. Neither flaw is in CISA's KEV catalog, and no public report ties either to an attack. The ESG carries history, though — UNC4841 exploited a different zero-day, CVE-2023-2868, in the same appliance line during the 2023 attacks, a case unrelated to this week's pair.

One operational note from the advisory: devices running firmware that is multiple versions out of date may need more than one update to reach the fixed release — and customers who turned automatic patching off should switch it back on.

What Should You Do?

  1. Patch every affected product now. ESG to 9.4.0.030+, and the fixed firmware listed per-product in Barracuda's advisory — if your firmware is several versions behind, plan for multiple update hops.
  2. Take administrative interfaces off the internet. The whole chain is gated on reaching the admin plane; restrict it to trusted internal networks and enforce network access controls around it.
  3. Re-enable automatic patching. Barracuda explicitly calls this out — appliances that silently fall behind on firmware are how "multiple versions out of date" happens.
  4. Run watchTowr's detection check and watch for the artifact of abuse. The tool flags vulnerable appliances today; the operational tell tomorrow is a configuration restore you did not perform — log and alert on backup-restore events.

The WAF Angle

The uncomfortable detail in this story is the product list: the Web Application Firewall and its Control Center are among the affected. The appliance class that exists to filter hostile HTTP is itself a web application with an admin plane, a session-handling bug, and a command injection — the exact vulnerability pairing we block in customer apps every day. The chain anatomy is a textbook case for why WAFs must be authorization-aware: step one is not an injection at all, it is a business-logic failure (failed password change → partial role assignment) that no signature will ever match, and it is followed by a "legitimate" restore operation that abuses a trusted feature. If your WAF cannot model "unauthenticated user reached an administrative function," it cannot see step one either. And the hardcoded checksum secret is the oldest crypto sin in embedded security — integrity checks are only as strong as the secrecy of the key behind them. The same admin-plane discipline we demanded after Ivanti's chained appliance zero-days and the exploited BeyondTrust edge flaw applies to the security stack itself.

Sources