The Spam Filter That Trusts Any Backup File

Barracuda ESG CVE-2026-116606 lets attackers restore a forged backup and get root; here's how to check and patch your clients' Barracuda ESG.

Imagine a bank vault that refuses your PIN, then politely asks if you would like to restore the vault from a backup you brought along. That is roughly what a Barracuda Email Security Gateway does with CVE-2026-116606: a failed password change leaves the door to the backup-restore feature open, and a timezone value hidden in that backup runs as a root command.

TL;DR

  • What happened: Barracuda Email Security Gateway (ESG) bugs CVE-2026-116606 and CVE-2026-111560 chain into root with no login; CISA added both to KEV on 10 November 2026.
  • Am I exposed: Any ESG on firmware before 9.4.0.030, per the CVE record, whose admin interface an attacker can reach, is open to the full chain.
  • What to do: Install patch BNSF-40425 or BNSF-40430 from Barracuda's advisory, and limit the admin interface to trusted internal networks.
  • Impact: Barracuda reports exploitation against "a small number of organizations", and the appliance sits in front of every inbound email.

What are CVE-2026-116606 and CVE-2026-111560?

CVE-2026-116606 is an authentication bypass in the Barracuda Email Security Gateway, and CVE-2026-111560 is a command injection; together they give an unauthenticated attacker root on the appliance. Barracuda published its advisory on 2 November 2026 and corrected it on 5 November to say CVE-2026-116606 needs no login, only access to the admin interface.

CVE-2026-116606 is rated 9.3 by Mandiant, which issued the CVE; NVD lists 9.8. CVE-2026-111560 is rated 8.6. The bypass affects only the ESG. The injection also hits the Load Balancer ADC, Message Archiver, WAF Control Center, Web Application Firewall and Web Security Gateway, but on those it still needs an administrator account.

How does the Barracuda ESG attack chain work?

The chain works in three moves, according to watchTowr's technical write-up:

  1. The failed password change. When a password change fails, the code returns a low-privilege role instead of stopping the request, so the request carries on into functions an anonymous visitor should never reach, including backup upload.
  2. The forged backup. Backups are protected by a checksum, but the secret behind it is hardcoded in the firmware. watchTowr published it ("Barracuda Networks is your new best friend"), so anyone can sign a fake backup.
  3. The poisoned timezone. During restore, the backup's system_timezone value is pasted into a shell sed command that runs as root. Put a command in the timezone field and the appliance runs it.

Is the Barracuda ESG flaw being exploited?

Yes. Barracuda updated its advisory on 9 November 2026 to report exploitation activity affecting "a small number of organizations", and CISA added both CVEs to its Known Exploited Vulnerabilities catalog on 10 November. SecurityWeek reported that federal agencies have three days to patch.

Scanning has started too. Previdian's sensor page counted 18 attempts against CVE-2026-116606 from 16 IP addresses between 9 and 11 November 2026 when we checked on 12 November. Nobody has publicly tied the activity to a named group, or to the 2023 ESG campaign.

Am I affected? How to check your clients' Barracuda ESG

Your clients are affected if they run an ESG below 9.4.0.030 and the admin interface is reachable by an attacker. Run these checks on all client appliances.

  1. Preserve evidence. On the syslog server that receives the appliance's logs, copy the logs and hash them before anyone patches or reboots:
D=/srv/ir/barracuda-$(date +%F); sudo mkdir -p "$D"
sudo cp -a /var/log "$D"/
sudo find "$D" -type f -exec sha256sum {} + | sudo tee "$D.sha256"
  1. Hunt for the restore. Search the copy, compressed files included, for the restore messages and audit action that watchTowr quotes (the "opertation" typo is Barracuda's). A restore nobody on the client's team ran is a red flag:
sudo find "$D" -type f -exec zgrep -HnE 'failed_password_change|Starting restore opertation|Untaring bundle|Finalizing restore' {} +
  1. Check the firmware. In the web interface, open ADVANCED > Firmware Update; the installed version is shown at the top of the page, per Barracuda's firmware docs. It passes at 9.4.0.030 or later.

  2. Test exposure from outside. From a machine outside the client's network, list each client's ESG hostname in esg-hosts.txt and run the loop below. Any status other than 000 means the admin page answers from the internet:

while read -r h; do
  printf '%s https:443 ' "$h"; curl -sk -o /dev/null -m 8 -w '%{http_code}\n' "https://$h/cgi-mod/index.cgi"
  printf '%s http:8000 ' "$h"; curl -s -o /dev/null -m 8 -w '%{http_code}\n' "http://$h:8000/cgi-mod/index.cgi"
done < esg-hosts.txt

Avoid running watchTowr's public "detection" script against client gear: its README shows it uploading a backup that executes a command on the target.

How do I fix CVE-2026-116606?

Patch first, then shrink the door.

  1. Preserve evidence with check 1 above before you touch the appliance.
  2. Install the patch. In ADVANCED > Firmware Update, set Apply Patches to Automatic, click Sync Now, and apply BNSF-40425 (ESG 9.4.017 and later) or BNSF-40430 (older builds), the IDs in Barracuda's advisory. Reboot if prompted, then confirm the version reads 9.4.0.030 or later.
  3. Lock down the admin interface. In BASIC > Administration, fill in Administrator/IP Range with the client's management subnet, as Barracuda's hardening guide describes; left empty, any address can log in. Rerun check 4 and confirm every line shows 000.
  4. Patch the other five products. Apply BNADC-16586 (Load Balancer ADC and WAF), BNMA-32468 (Message Archiver), BNWF-60060 (WAF Control Center) and BNYF-24789 (Web Security Gateway), then confirm each device's firmware page lists the patch.
  5. Escalate any hit. If check 2 found a restore nobody planned, block the admin interface at the client's firewall, email [email protected] from the advisory with the evidence hash file, and keep the block until Barracuda confirms the appliance is clean.

Edge-appliance logins keep failing this way: see how attackers skipped MFA on SonicWall VPNs.

Where KinoSec fits

This bug comes down to one question: can an attacker reach the admin page? An external network pentest answers it, finding which client hosts expose management interfaces to the internet, flagging known-vulnerable services and writing up the fix. KinoSec runs that test autonomously and on demand, so you can sweep your whole client portfolio the week a KEV entry lands. Start with autonomous external and internal network pentesting with Poseidon, and hand each client a report that shows exactly which appliance answered and what you closed.

Frequently Asked Questions

Is the Barracuda Email Security Gateway vulnerability being exploited?

Yes. Barracuda reports exploitation of CVE-2026-116606 and CVE-2026-111560 affecting "a small number of organizations", and CISA added both to its Known Exploited Vulnerabilities catalog on 10 November 2026. Previdian's sensors counted 18 attempts from 16 IP addresses between 9 and 11 November 2026.

How do I check if my clients were hit by CVE-2026-116606?

First, copy and hash the syslog server's logs with sudo cp -a /var/log "$D"/ followed by the sha256sum step in the article. Second, search the copy for failed_password_change and Starting restore opertation with zgrep; a restore no one planned is a red flag. Third, open ADVANCED > Firmware Update on the appliance and confirm the version is 9.4.0.030 or later.

Do Barracuda WAF and Load Balancer need patching too?

Yes. CVE-2026-111560 also affects the Load Balancer ADC, Message Archiver, WAF Control Center, Web Application Firewall and Web Security Gateway, though on those products it needs an administrator account. Barracuda's advisory lists the patch IDs.

Can an autonomous pentest find an exposed Barracuda admin page?

Yes. A KinoSec external network pentest finds client hosts that expose management interfaces to the internet and flags known-vulnerable services, with remediation in the report. It does not replace Barracuda's patch.