Skip to content
Log inRegister

Barracuda Email Security Gateway: Two Flaws Chain to Root With No Login

Dr. Abeer Alshammari · Published 11/6/2026 · Updated 11/7/2026

IntermediateProfessionalsCISOs
Developing story: patched, not yet exploited publicly

As of this week neither flaw appears in CISA KEV and no public report ties either to an attack. watchTowr has released a detection tool but not an exploit.

What happened

Barracuda released patches on Monday for two flaws in its Email Security Gateway, an appliance that filters email. On Thursday watchTowr Labs published an analysis showing the two can be chained to reach root with no login.

How the chain works

The first flaw, CVE-2026-116606, is an authorization bypass. A failed password change returns a low-privilege role instead of stopping the request, which leaves a backup-restore function open to someone who has not logged in. That function accepts an uploaded configuration backup and lets the attacker change global settings.

The second flaw, CVE-2026-111560, is a command injection that normally needs an administrator account. The restored data includes a timezone value that the appliance later runs as a shell command with root privileges. Barracuda protects backups with a checksum, but the secret used to compute it is built into the code, so an attacker can forge a valid one. Chained, the two flaws give root without credentials.

Who is affected

The authorization bypass affects only the Email Security Gateway. The command injection reaches five other Barracuda products, but on those it still needs an administrator account. The Email Security Gateway is fixed in firmware 9.4.0.030 and later.

Technical impact

FieldDetail
CVEsCVE-2026-116606 (authorization bypass), CVE-2026-111560 (command injection)
Severity9.3 and 8.6, as rated by Mandiant
Result when chainedCommands as root, no authentication
Fixed firmwareEmail Security Gateway 9.4.0.030 and later
CISA KEVNot listed as of this week
Public toolingDetection tool released; no exploit published

Governance impact

Security appliances sit at the edge with high privilege and are often outside normal patch cycles. Email gateways were attacked in 2023 through a different Barracuda flaw, which is unrelated to these two, but it shows why appliances deserve their own owner and patch deadline.

What security teams should do

  • Apply the patch for each affected Barracuda product, or upgrade to the fixed firmware
  • Limit the appliance administration interface to trusted internal networks if you cannot patch at once
  • Turn automatic patching back on if it was disabled
  • Use the public detection tool to check whether an appliance is vulnerable

What executives should know

This is a window between a patch and likely attacker interest. The organization has a short period to confirm that every email gateway is updated before exploit code appears.

Dr. Abeer Takeaway

Ask whether security appliances are in the asset inventory with a named owner. Edge devices that no one owns are the ones patched last, and attackers know it.

GCC Relevance

Email security gateways are common in GCC enterprises and government bodies. Confirm firmware versions rather than assuming a managed service has applied the update.

Sources

  1. [1]Pre-authentication authorization bypass and command injection advisory — Barracuda Networks (11/2/2026)Accessed 11/7/2026
  2. [2]Barracuda Email Security Gateway pre-auth remote root RCE analysis — watchTowr Labs (11/5/2026)Accessed 11/7/2026
  3. [3]Experts Demonstrate Barracuda Email Security Gateway Chain Enabling Root Access Without Login — The Hacker News (11/6/2026)Accessed 11/7/2026

Try it yourself

An interactive CyberAbeer experience for this topic is in development.

Coming soon
Back to insights