Barracuda published one advisory page for two flaws on 2 November 1. CVE-2026-116606 is a pre-authentication authorization bypass that Barracuda scores 9.3, and it affects the Email Security Gateway alone 1. CVE-2026-111560 is an OS command injection at 8.6, and it runs across six product lines: the gateway, the load balancer ADC, the Message Archiver, the WAF Control Center, the Web Application Firewall, and the Web Security Gateway 1. Barracuda states that used in combination the pair can “bypass authorization controls and obtain root access to the device” 1. Mandiant published the technical advisory for the bypass the same day, and NVD’s record credits Mandiant as its source 23.

The login that did not stop the request

watchTowr compared the patched build against 9.4.0.027 and put the bypass in the password change handler 4. In the vulnerable code, a failed password change returns the current session’s role object, and the routine that ends the request never runs. Execution falls through into the module handlers behind the password form, which keep working with the login screen’s low-privilege role 4.

Nothing in that request carries a credential. The admin interface has to answer it for the bypass to work.

A backup restore with a shell in the middle

CVE-2026-111560 supplies the second half. watchTowr traced it to the timezone handling in the backup restore path. The value stored in system_timezone goes into a sed command through Perl backticks, so a crafted timezone string closes the quoting, starts a new command, and comments out the rest of the line 4. The patch rejects any timezone that does not resolve to a file under /usr/share/zoneinfo/, and replaces the shell call with a read, rewrite, write of the config file 4.

The restore path holds a second weakness. Each file in a backup archive lists an MD5 checksum, and the restore validates that checksum before it uses the file. The string the restore appends to those file bytes before hashing is a fixed value in every copy of the product, Barracuda Networks is your new best friend, and watchTowr reused it to pack an archive the appliance accepts 4. An attacker who can compute the same checksum gets the archive past that check 4.

The field the advisory corrected

Barracuda changed one line on 5 November. The Authentication Required field for CVE-2026-116606 went from “Yes, administrative access” to “No (Administrative UI Access Required)”, with the note that the flaw needs no authentication, though exploitation requires the admin interface to be reachable 1.

That correction moves the gate from a credential to a network path. The advisory’s guidance follows the same line: organizations whose administrative interfaces are not publicly accessible from the internet are less exposed, and Barracuda recommends restricting those interfaces to trusted internal networks 1. On an edge appliance, the reachability of the management interface is the first thing I ask about, because an admin page that answers from the internet carries this exposure on its own.

One appliance patched, five left on the page

The gateway ticket covers one product. Barracuda ships BNSF-40425 for appliances on 9.4.017 and later and BNSF-40430 for anything older, and either patch closes CVE-2026-116606 and the injection on the gateway 1. NVD lists builds earlier than 9.4.0.030 as affected 3. The other five lines each need their own patch: BNADC-16586 for the ADC and the Web Application Firewall, BNMA-32468 for the Message Archiver, BNWF-60060 for the WAF Control Center, and BNYF-24789 for the Web Security Gateway 1.

The gateway build does not cover those five appliances, and none of them appears in a ticket opened against the gateway. CVE-2026-111560 needs an authenticated administrator session on its own, which is why it reads as lower priority than a 9.3 bypass that needs no credential 1. CISA put the same deadline on that one: it added CVE-2026-111560 in the same 10 November batch, due 13 November with forensic triage required, and the record covers all six product lines, not the gateway alone 5. It still matters for the estate. Barracuda describes the pair reaching root, and the second half of that pair sits on five products the gateway patch does not touch 1.

The tooling and the clock

watchTowr published a working tool with the write-up, so the chain does not depend on anyone’s private research 4. CISA added CVE-2026-116606 to the KEV catalog on 10 November with a due date of 13 November, and the entry requires forensic triage under BOD 26-04 5. Barracuda’s 9 November update reports exploitation activity against a small number of organizations 1.

The relay list

First, the build on each appliance, read from the device. A line in a deployment record says what someone intended to run, and the appliance reports what it is running.

Second, which network every admin interface answers on, across all six product lines. A gateway on a private management network and an ADC with a login page on the internet are different exposures, and I want both answers on the same page of the note.

Third, the patch ID per product. A change ticket named after the gateway can close while five appliances behind it keep the injection.

Fourth, for every gateway that answered on its admin interface while unpatched, a configuration review. The bypass restores a backup archive, and the restore rewrites the appliance’s global configuration 2. The comparison I want is the configuration now against a known-good export from before 2 November, with a read of whatever decides where mail goes and who can log in.

Fifth, the logs. The restore arrives inside a request to the admin interface 4, and the appliance’s own records are the only account of which requests came in before the patch. I pull them and keep a copy off the device, because the copy on a box that may have been restored from a crafted archive is the copy I trust least.

What the patch does not restore

The upgrade closes the bypass and the injection. It does not undo a configuration that a restore rewrote, an administrator account that appeared while the interface answered without a login, or a filter that now sends mail somewhere else. Those are separate checks with separate evidence, and the KEV date is a deadline for the first one only.

I plan the relay around the product lines on the advisory page, because the five appliances that need a separate patch will not appear in a ticket about the gateway.


  1. Barracuda Networks. (2026, November 2). Pre-authentication authorization bypass and command injection vulnerabilities in certain Barracuda products (updated November 9, 2026). Barracuda Trust Center. https://trust.barracuda.com/security/pre-authentication-authorization-bypass-command-injection ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  2. Mandiant. (2026, November 2). MNDT-2026-0042: Barracuda Email Security Gateway authentication bypass (CVE-2026-116606). GitHub. https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0042.md ↩︎ ↩︎

  3. National Vulnerability Database. (2026, November 2). CVE-2026-116606 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-116606 ↩︎ ↩︎

  4. watchTowr Labs. (2026, November 5). Barracuda Networks is your new best friend: Barracuda Email Security Gateway pre-auth remote root RCE, CVE-2026-116606 and CVE-2026-111560. https://labs.watchtowr.com/barracuda-networks-is-your-new-best-friend-barracuda-email-security-gateway-pre-auth-remote-root-rce-cve-2026-116606-cve-2026-111560/ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  5. Cybersecurity and Infrastructure Security Agency. (2026, November 10). Known exploited vulnerabilities catalog (CVE-2026-116606 and CVE-2026-111560). https://www.cisa.gov/known-exploited-vulnerabilities-catalog ↩︎ ↩︎