Barracuda CVE-2026-116606 and CVE-2026-111560: Patches and Checks

Two exploited Barracuda flaws can be chained: an attacker who can reach the Email Security Gateway admin interface can skip the login, change the configuration and get root. The command injection half also affects five other Barracuda products.

Find your patch
By CalMax Systems Security Research · Published November 18, 2026 · Last updated: November 18, 2026

What are CVE-2026-116606 and CVE-2026-111560, and how do I fix them?

CVE-2026-116606 (CVSS 4.0 score 9.3) is an authentication bypass in Barracuda Email Security Gateway (ESG): without logging in, an attacker can restore a crafted backup and change the appliance’s global configuration. CVE-2026-111560 (CVSS 4.0 score 8.6) is an OS command injection in the timezone setting that runs commands as root for an administrator. Barracuda says the two together could give an attacker root on the device.

Fix: run the latest firmware with all security patches. On ESG that is patch BNSF-40425 (firmware 9.4.017 and later) or BNSF-40430 (older than 9.4.017). Keep the admin interface off the internet. Barracuda has seen exploitation at a small number of organizations, and CISA added both CVEs to its Known Exploited Vulnerabilities catalog on November 10, 2026.

Affected Products and Patches

Patch IDs are from Barracuda’s advisory (published November 2, 2026; last updated November 9, 2026). Affected versions come from two places that do not agree: the CVE records, published by Mandiant as the CVE numbering authority, and NVD’s own analysis. Where NVD specifies appliance models, its firmware cutoffs apply to the listed models. The Trust Center advisory lists patch IDs. Barracuda Campus also publishes product-specific firmware and patch instructions.

Product CVE-2026-116606 (auth bypass) CVE-2026-111560 (command injection): CVE record CVE-2026-111560: NVD analysis Barracuda patch and Campus firmware guidance
Email Security Gateway (ESG)Yes: versions earlier than 9.4.0.030 (CVE record and NVD agree)Yes: 9.4.0.27 and earlierEarlier than 9.4.0.029BNSF-40425 (9.4.017 and later)
BNSF-40430 (earlier than 9.4.017)
Campus says 9.4.0.029 includes the updates. The CVE record lists 9.4.0.030 as the first version outside the affected range for CVE-2026-116606. Given the discrepancy, target 9.4.0.030 or later and verify the applicable security patch. If 9.4.0.030 or later is unavailable for your appliance, ask Barracuda Support to confirm remediation.
Load Balancer Application Delivery Controller (ADC)NoYes: 6.4.0 and earlierEarlier than 6.4BNADC-16586
Campus documents a patch for 6.4 through 6.6.0.009. On firmware 6.4 through 6.6.0.009, the patch installs automatically if Apply Patches is set to Automatically. For older firmware, follow the Campus upgrade path. Barracuda lists 6.4 as the minimum for the patch procedure and directs appliances on versions it describes as earlier than 6.3.0.0xx to upgrade to 6.6.0.009 or later. Verify that BNADC-16586 is installed and reboot if prompted.
Message Archiver (BMA)NoYes: 5.5.4.0 and earlierEarlier than 5.5.4.002BNMA-32468
Campus lists firmware 5.2 through 5.5.4.001 as affected. Versions 5.2 through 5.4.x require a manual upgrade to 5.5.4.002. Accept the reboot prompt, then confirm version 5.5.4.002 or later under Advanced > Firmware Update. Versions 5.5.0 through 5.5.4.001 receive the patch automatically without a version change. Firmware 5.5.4.002 includes the patch. The CVE record also lists builds earlier than 5.2 as affected, and Campus gives no procedure for them; contact Barracuda Support for an upgrade path.
WAF Control Center (WCC)NoYes: 2.2.1 and earlierNot listedBNWF-60060
Campus documents a patch for 2.2.1 through 2.4.1.001. For appliances below 2.2.1, Campus specifies an upgrade target of 2.4.1.001 or later. The numbered patch procedure lists 2.2.1 as the minimum firmware for that procedure. Verify that BNWF-60060 is installed and reboot if prompted.
Web Application Firewall (WAF)NoYes: 11.0.1 and earlierEarlier than 12.3.1.002BNADC-16586
Campus documents a patch for 11.0.1 through 12.3.0.011. For appliances below 11.0.1, Campus specifies an upgrade target of 12.3.0.011 or later. The numbered patch procedure lists 11.0.1 as the minimum firmware for that procedure. Before upgrading, back up the configuration and read the release notes for each firmware version you will apply. If the upgrade crosses into 12.2 or later, replace MD5- or SHA-1-signed certificates with SHA-256-signed certificates first; the 12.2 release notes warn that services using them will go down and rollbacks occur. Verify that BNADC-16586 is installed on builds that need the separate patch and reboot if prompted. The 12.3.1.002 release notes confirm that this WAF build includes the fix and requires no separate patch.
Web Security Gateway (WSG)NoYes: 16.1.100.100 and earlierEarlier than 15.0.0.009BNYF-24789
Campus documents updated firmware from 15.0.0.009 through 16.1.003 and directs appliances on 15.0 or earlier to upgrade to 15.0.0.009 or later. Apply the security update on appliances in the documented range, reboot if prompted, and return to Advanced > Firmware Update to confirm the installed version. If your build falls outside Campus’s documented update range and is still listed as affected by the CVE record, ask Barracuda Support to confirm the fix for that build.
Go by the patch, not the version number alone. Barracuda Campus labels ESG, ADC, WCC, WAF and WSG as affected across all versions and provides firmware-specific instructions for applying and verifying the updates. Its Message Archiver guidance gives a bounded affected range. Run the latest firmware available for your appliance and use the product-specific Campus instructions to verify that it has the security fix. For firmware that includes the fix, verify the installed build. Where a separate patch is required, verify that it was applied. Barracuda Support (support@barracuda.com) can help confirm both.

What the Two Flaws Do

One flaw gets an attacker past the login. The other turns admin access into root.

CVE-2026-116606, authentication bypass (ESG only). The CVE record describes an authentication bypass in Email Security Gateway versions earlier than 9.4.0.030 that “allows an unauthenticated remote attacker to invoke a configuration-import function and restore a crafted, compatible backup archive, resulting in unauthorized modification of the appliance’s global configuration.” It is classed as CWE-288, authentication bypass using an alternate path or channel. The CVSS 4.0 score is 9.3; NVD scores it 9.8 under CVSS 3.1. Both scores are rated Critical in those records; Barracuda’s advisory labels its severity High.

Barracuda first listed this CVE as needing administrative access. On November 5, 2026 it corrected the advisory: authentication is not required, but the attacker must be able to reach the ESG administrative user interface (Admin UI).

CVE-2026-111560, OS command injection (six products). Shell metacharacters in the timezone configuration field are not neutralized, so “an authenticated administrator” can inject OS commands “that execute with root privileges when the crafted timezone value is subsequently processed.” It is CWE-78. The CVSS 4.0 score is 8.6, with high privileges required; NVD scores it 7.2 under CVSS 3.1. The flaw sits in common Barracuda code shared by ESG, ADC, BMA, WCC, WAF and WSG.

The chain. Barracuda says that “if exploited in combination, these vulnerabilities could allow an attacker to bypass authorization controls and obtain root access to the device,” and CISA’s catalog says each CVE can be chained with the other. Because only ESG has the authentication bypass, ESG is the product open to the full chain without a password. On the other five products, CVE-2026-111560 needs an administrator login.

Is your appliance at risk? Barracuda says successful exploitation “requires an attacker to have access to the administrative interface of an affected product,” and that organizations whose administrative interfaces are not publicly accessible from the internet are less exposed. An ESG with an unpatched firmware and an admin interface reachable from the internet is the highest-risk case.

How to Check Your Firmware and Exposure

Use the Barracuda Campus guide for your product. On ESG, open Advanced > Firmware Update. Firmware below 9.1 requires a two-step upgrade. Before upgrading, back up the configuration, read the release notes for the intervening versions, and take ESG offline using Basic > Administration so the inbound queue can drain. Do not manually reboot during the upgrade unless Barracuda Support directs you to do so. For clustered ESG appliances, use Advanced > Clustering to put each member in Standby before upgrading it. Reboot each member if prompted and verify its firmware and patch. Return the members to Active after all have been upgraded. Bring ESG back online after the upgrade and verify mail flow. If you upgraded to 9.4 from an older branch and use Bayesian filtering, retrain the Bayesian database. Check mail flows that rely on DKIM verification. Starting in 9.4, RSA-SHA1 signatures fail verification, and the DKIM l= tag must cover the full message body.

1. List every affected appliance

Include ESG, Load Balancer ADC, Message Archiver, WAF Control Center, WAF and Web Security Gateway, physical and virtual. Older or forgotten units count; the command injection affects all six products.

2. Check the firmware and the patch

  • Sign in to each appliance’s web interface and note the firmware version. Barracuda says the device shows the latest firmware version available.
  • If the appliance is behind the latest version, update it. Barracuda notes that a device several versions behind may need more than one update.
  • Use the table above to confirm that your firmware includes the fix or that the separate patch was applied. If your build requires a separate patch and it was not applied automatically, apply it manually. Barracuda recommends re-enabling automatic patching if it was turned off.

3. Check who can reach the admin interface

  • Find which addresses and ports the admin web interface listens on, and whether any firewall rule, NAT rule or cloud security group exposes them to the internet.
  • From an untrusted external network, test your appliance’s configured public management hostnames, addresses, and web interface ports. If you reach the Barracuda administrator login page, the Admin UI is exposed. Confirm the result against the network access rules for every management endpoint.
  • Restrict the administrative interface to trusted internal networks using network access controls.

What to Do Now

Barracuda’s remediation for both CVEs is the latest firmware with all security patches. Restricting access reduces the risk; patching removes it.

Update firmware and verify the patch

Follow the Campus instructions for your product. Verify that the latest firmware available for your appliance includes the fix or has received the separate patch specified by Campus. If a patch has not been applied automatically, Barracuda says to apply the appropriate patch manually as soon as possible. Barracuda Campus explains how to apply a patch or update firmware by hand. Contact Barracuda Support at support@barracuda.com if you need help verifying the version or applying the patch.

Take the admin interface off the internet

Barracuda recommends restricting access to administrative interfaces to trusted internal networks and using network access controls to limit exposure. Allow the admin UI only from trusted internal networks, such as a dedicated management network. Keep the restriction in place after you patch.

Protect administrator accounts

On an unpatched appliance, an authenticated administrator can exploit CVE-2026-111560 to execute commands as root. Review administrator accounts and privileges during triage, and coordinate credential rotation through your incident response process if compromise is suspected.

Check for Signs of Compromise

Patching closes the flaws. It does not undo changes an attacker made before you patched.

Public indicators and forensic triage

Barracuda’s advisory, CISA’s catalog entries and the Mandiant disclosures list no IP addresses, file hashes or other indicators of compromise for these CVEs. CISA flags both CVEs for forensic triage under BOD 26-04. Its implementation guidance directs in-scope agencies to collect evidence before altering or patching affected systems when possible. The checks below are starting points and cannot rule out compromise. For in-scope federal agencies, CISA calls for a forensic triage report. If compromise is suspected, continue triage and coordinate next steps with CISA. If the agency’s top-level incident response, security operations, or IT team identifies an incident that potentially compromises the confidentiality, integrity, or availability of a federal civilian executive branch information system, notify CISA through the CISA Incident Reporting System within one hour of identification. Submit the information available at that point and update the report as findings are validated.

What to review

  • CVE-2026-116606 works by restoring a crafted configuration backup. Compare the current ESG configuration with your own last known-good backup and look for settings no one on your team changed: administrator accounts and passwords, allowed admin addresses, mail routing and relay settings, and the timezone setting.
  • Review logs for unexplained administrator logins and configuration changes, including restore or import events if recorded. On ESG, use Advanced > Troubleshooting > Monitor Web Syslog to inspect the local web log. If ESG was already forwarding logs to a syslog server, review its debug-priority Web syslog records for configuration changes. Use firewall connection logs to corroborate when and from where the admin interface was reached.
  • Check how long the Admin UI was reachable from the internet. If it was, review logs as far back as they go.
  • If you find anything you can’t explain, treat it as an incident: preserve logs and volatile evidence before altering or patching the appliance when possible, contact Barracuda Support, and coordinate isolation and credential rotation through your incident response process. Code that ran as root can leave changes a configuration review will not show.

Timeline

DateEvent
October 15, 2026CVE-2026-111560 reported by Barracuda (Mandiant disclosure timeline).
October 22, 2026CVE-2026-116606 reported by Barracuda (Mandiant disclosure timeline).
November 2, 2026Barracuda publishes its advisory with patches. Both CVEs and the Mandiant advisories are published.
November 5, 2026Barracuda corrects the advisory: CVE-2026-116606 needs no authentication, only access to the Admin UI.
November 9, 2026Barracuda adds that it has identified exploitation activity affecting a small number of organizations.
November 10, 2026CISA adds CVE-2026-116606 and CVE-2026-111560 to the Known Exploited Vulnerabilities catalog.
November 13, 2026Remediation due date shown in CISA KEV for both CVEs. Federal civilian agencies determine the applicable deadline for each asset under BOD 26-04. CISA directs agencies to apply vendor mitigations, follow the applicable BOD guidance for cloud services, and discontinue use of the affected product if mitigations are unavailable.

Where ThreatListPro Fits

A known-attacker list helps at the VPN edge. It does not fix these flaws.

Both CVEs need access to the Barracuda admin interface, so the fix is the patch, and the lasting control is an admin interface that only trusted internal addresses can reach. Barracuda’s advisory and CISA’s KEV entries list no attacker IP addresses for these CVEs.

ThreatListPro is for the logins your firewall has to expose, such as SSL-VPN and GlobalProtect portals. It covers 5.4M+ IPv4 addresses from real attacks on live production Palo Alto GlobalProtect VPN portals in the US and is checked for new attackers every 6 hours. A deny rule that uses it rejects listed sources before they can try a password. Block an IP Address at the Firewall shows how a list like this is used, and the guides below cover each firewall.

Barracuda CVE-2026-116606 and CVE-2026-111560 FAQs

Are CVE-2026-116606 and CVE-2026-111560 being exploited?

Yes. On November 9, 2026, Barracuda updated its advisory to say it has identified exploitation activity affecting a small number of organizations. CISA added both CVEs to its Known Exploited Vulnerabilities catalog on November 10, 2026, with November 13, 2026 as the catalog remediation due date. US federal civilian agencies determine the applicable deadline for each asset under BOD 26-04.

Are the two Barracuda flaws a chain?

Yes. CVE-2026-116606 is an authentication bypass in Email Security Gateway (ESG) that lets an unauthenticated attacker restore a crafted backup and change the appliance’s global configuration. CVE-2026-111560 is a command injection in the timezone setting that runs commands as root for an administrator. Barracuda says that, used together, they could let an attacker bypass authorization controls and get root access. CISA’s catalog says each can be chained with the other.

Which Barracuda products are affected?

CVE-2026-116606 affects only Email Security Gateway (ESG). CVE-2026-111560 affects ESG, Load Balancer Application Delivery Controller (ADC), Message Archiver (BMA), WAF Control Center (WCC), Web Application Firewall (WAF) and Web Security Gateway (WSG). Only ESG is affected by both, so only ESG is exposed to the full unauthenticated chain.

Which patch fixes the Barracuda ESG flaws?

Barracuda lists patch BNSF-40425 for ESG firmware 9.4.017 and later, and BNSF-40430 for ESG firmware older than 9.4.017. Barracuda Campus says ESG firmware 9.4.0.029 includes the updates. The CVE record still lists versions earlier than 9.4.0.030 as affected by CVE-2026-116606. Install the latest available firmware and verify the applicable patch. Barracuda says to run the latest firmware with all security patches applied, and to apply the patch by hand if it was not applied automatically. Given the difference between Campus and the CVE record, target 9.4.0.030 or later and ask Barracuda Support to confirm remediation if that version is unavailable for your appliance.

Does an attacker need a password to exploit CVE-2026-116606?

No. Barracuda changed the advisory on November 5, 2026 to say authentication is not required, but the attacker must be able to reach the ESG administrative user interface. CVE-2026-111560 on its own does need administrator access.

Is there a workaround for the Barracuda flaws?

Barracuda’s fix is to upgrade to the latest firmware and apply the patch. It also says organizations whose administrative interfaces are not reachable from the internet are less exposed, and recommends restricting admin interfaces to trusted internal networks with network access controls. That reduces the risk; only the patch fixes the flaws.

Are there indicators of compromise for these Barracuda CVEs?

Barracuda’s advisory, CISA’s catalog entries and the Mandiant disclosures publish no IP addresses, file hashes or other indicators. CISA flags both CVEs for forensic triage. Review configuration changes and administrator accounts, and contact Barracuda Support if anything is unexplained.

Sources

Block Known VPN Attackers at Your Firewall

ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial and no card needed.

Start a 14-day free trial Or test the free sample first: no signup

Firewall Guides

ThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

More dated alerts on exploited edge devices, and how to lock down what faces the internet.

All Security Alerts PAN-OS CVE-2026-0322: Fixed Versions and Mitigations Ivanti Connect Secure CVE-2026-104935 Block an IP Address at the Firewall Password Spraying on VPNs VPN Brute Force Explained