On this page (7 sections)

Barracuda has patched two flaws in its products that, when chained, can give an attacker root access to an Email Security Gateway (ESG) appliance. The first, CVE-2026-116606, is a pre-authentication authorization bypass that affects only the ESG. The second, CVE-2026-111560, is a command injection that normally needs an administrator account. On the ESG, the bypass supplies that access.

CISA added CVE-2026-116606 to its Known Exploited Vulnerabilities catalog on 2026-11-10, and Barracuda has said it identified exploitation activity affecting a small number of organizations. If you run an ESG appliance, treat this as a patch-now item and check who can reach its administration interface.

What happened

Barracuda disclosed a pre-authentication authorization bypass and a command injection, tracked as CVE-2026-116606 and CVE-2026-111560. The Hacker News reported that Barracuda said exploiting them together could let an attacker bypass authorization controls and obtain root access to the device.

The security firm watchTowr then published a technical analysis of the chain, according to a second Hacker News report. That report said watchTowr also released a tool for checking whether an appliance is vulnerable, but did not publish an exploit. For the second flaw in the chain, see our separate write-up of CVE-2026-111560.

Exploitation status: what the sources say

The sources were published at different times, so they differ. The November 6 report said neither flaw was in the CISA KEV catalog and no public report tied either to an attack. That is now out of date. The NVD record and CISA's catalog data show CVE-2026-116606 was added on 2026-11-10, and an update to the November 3 report says Barracuda confirmed on November 9 that it had identified exploitation activity affecting a small number of organizations. Barracuda's statement, as quoted, did not say which flaw was involved or give further details, and the research does not name any attacker. CISA lists ransomware use as unknown.

Technical details

The bypass is a weakness in how the appliance decides who may call a sensitive function. Per the CVE description, an unauthenticated remote attacker can invoke a configuration-import function and restore a crafted, compatible backup archive, which modifies the appliance's global configuration. The CVSS v4 metrics in the GitHub advisory list network attack vector, low complexity, no privileges and no user interaction.

According to watchTowr's analysis as summarized by The Hacker News, a failed password change returns a low-privilege role instead of stopping the request. That leaves the backup-restore function open to someone who has not logged in. The restored data includes a timezone value that the appliance later runs as a shell command with root privileges. Backups are protected by a checksum, but the secret used to compute it is built into the code, so a valid checksum can be forged.

In plain terms, the chain has three parts: skip the login check, feed the appliance a configuration it trusts, and let a value in that configuration reach a root-level command. NVD notes that CVE-2026-116606 can be chained with CVE-2026-111560. Our reasoning, not a vendor statement: since the chain is what yields root with no login, applying the fixed firmware is the safest response, and network restrictions are a stopgap.

Who is affected

  • Anyone running Barracuda Email Security Gateway on a version earlier than 9.4.0.030. The bypass affects only this product.
  • Appliances whose administrative interface is reachable from the internet or from broad internal networks. Barracuda said organizations that do not expose the admin interface to the internet are less vulnerable to this attack path.
  • Owners of the other Barracuda products affected by CVE-2026-111560. The sources disagree on the count: one Hacker News report says five other products, while another lists six besides the ESG (Load Balancer, Application Delivery Controller, Message Archiver, WAF Control Center, Web Application Firewall and Web Security Gateway). Check Barracuda's advisory for the authoritative list. The Hacker News reports that on those products the command injection still requires administrator access, and…
  • Appliances with automatic patching turned off, which may be several firmware versions behind.

For context, ESG appliances were targeted in 2023 by a group tracked as UNC4841 using a different flaw, CVE-2023-2868. The Hacker News notes that case is unrelated, and nothing in the research ties the new flaws to any attacker.

How to check your exposure

Start with the firmware version shown in the appliance's administration interface and compare it with 9.4.0.030. Then check where that interface is reachable from. The command below sends one request to your appliance's admin interface and prints only the HTTP status code. Run it from a machine outside your network, replacing the placeholders with your own admin hostname and port. If a status code is printed, the interface answers from wherever you ran the test.

Check whether the admin interface answers from outside your network (run from an external host)Shell
curl -sk -o /dev/null -w "%{http_code}\n" --max-time 10 https://<your-esg-hostname>:<admin-port>/

A timeout or connection error is the result you want from the internet. watchTowr's detection tool can also test whether an appliance is vulnerable; review it before running it against production.

What to do now

Caution. Firmware updates are a change to a production mail appliance. Plan a maintenance window and read Barracuda's advisory first. If the device is multiple versions out of date, Barracuda says you may need to perform more than one update.
  1. Update every affected Barracuda product to the fixed firmware listed in Barracuda's advisory. For Email Security Gateway that is 9.4.0.030 or later.
  2. If you turned automatic patching off, switch it back on, as the advisory recommends.
  3. If you cannot patch immediately, restrict the administration interface to trusted internal networks and use network access controls to limit exposure.
  4. Confirm after the update that the version shown is 9.4.0.030 or later, and that the admin interface is not reachable from the internet.
  5. Because exploitation has been confirmed, review the appliance for unexpected configuration changes, unknown admin accounts, restored backups you did not initiate, and unfamiliar files or outbound connections.
  6. CISA's KEV entry names its 'Forensics Triage Requirements' guidance as part of the required action. If you are subject to it, read that guidance before changing the device.
  7. If you find signs of tampering, treat the appliance as compromised: rotate credentials and keys stored on or passing through it, and follow our guide on what to do when a website is hacked.
The CISA KEV due date for federal agencies is 2026-11-13. Other organizations are not bound by it, but it signals how quickly CISA expects this to be handled.

Detection and monitoring

Appliance flaws are easy to miss because they sit outside your usual patching tools. Keep an inventory of every Barracuda device and its firmware version, and subscribe to the vendor's security notices. Alert on configuration restores and changes to global settings, and on administrative logins from unfamiliar addresses.

On the web-facing side, Webforta Monitor can watch uptime, certificate and DNS changes for your mail and admin hostnames, which helps you notice unexpected changes around a gateway. It does not detect this vulnerability or patch the appliance. For general guidance on reviewing what your site exposes, see security for small business websites.

Timeline

Key events as given in the sources
DateEvent
2026-11-02CVE-2026-116606 published to NVD and the GitHub Advisory Database
Monday before Nov 6 (per The Hacker News, reported Nov 6)Barracuda released patches
2026-11-03The Hacker News reports on Barracuda's disclosure and mitigation guidance
Thursday before Nov 6 (per The Hacker News, reported Nov 6)watchTowr detailed the attack chain and released a detection tool
2026-11-09Barracuda confirmed it identified exploitation activity affecting a small number of organizations
2026-11-10CVE-2026-116606 added to CISA KEV; federal due date 2026-11-13

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-116606 - GitHub Advisory Databasegithub.com
  2. Barracuda Networks Email Security Gateway (ESG) Authentication Bypass Using an Alternate Path or Channel Vulnerability (CVE-2026-116606) is being actively exploitednvd.nist.gov ·
  3. Experts Demonstrate Barracuda Email Security Gateway Chain Enabling Root Access Without Loginthehackernews.com ·
  4. Barracuda Flaws Could Be Chained to Bypass Authorization and Gain Root Accessthehackernews.com ·
  • Barracuda
  • CVE-2026-116606
  • CISA KEV
  • email security
  • authentication bypass