Skip to content

Barracuda ESG CVE-2026-116606 and CVE-2026-111560: Patch the Exploited Auth Bypass to Root Chain

Barracuda ESG's exploited CVE-2026-116606 chains with CVE-2026-111560 for root. Patch IDs for ESG, ADC, WAF, WSG, BMA and WCC, admin UI lockdown and checks.

MGMCSA Guru Team November 20, 2026 6 min read
An email security gateway appliance with its admin door ajar as a backup box is slid inside, a glowing clock dial and a closing gate in front

Barracuda has patched two vulnerabilities that, used together, let an attacker who can reach the admin interface of an Email Security Gateway (ESG) bypass authorization and get root on the appliance. CVE-2026-116606 is a pre-authentication authorization bypass in ESG. CVE-2026-111560 is a command injection that also affects Barracuda’s Load Balancer ADC, Web Application Firewall, Web Security Gateway, Message Archiver and WAF Control Center.

Barracuda’s advisory, updated November 9, 2026, says “We have identified exploitation activity affecting a small number of organizations.” CISA added both CVEs to its Known Exploited Vulnerabilities (KEV) catalog on November 10 and set its forensic triage flag on both. If you run any of these appliances, check that the patch for your product is applied, and check whether the admin UI is reachable from the internet.

How the CVE-2026-116606 chain works

The two bugs do different things, and only the combination gives root:

  1. CVE-2026-116606 (ESG only). The CVE record, assigned by Mandiant, says an authentication bypass in ESG versions earlier than 9.4.0.030 lets an unauthenticated remote attacker invoke a configuration-import function and restore a crafted, compatible backup archive. The result is unauthorized modification of the appliance’s global configuration.
  2. CVE-2026-111560 (six products). The timezone configuration field doesn’t neutralize shell metacharacters. An authenticated administrator can inject OS commands that run with root privileges when the crafted timezone value is processed.

On its own, CVE-2026-111560 needs administrator access, and CVE-2026-116606 changes configuration rather than running commands. Barracuda says that “if exploited in combination,” they could let an attacker bypass authorization controls and obtain root access to the device. CISA’s KEV entries also note that the two can be chained.

Barracuda corrected one detail on November 5: the “Authentication Required” field for CVE-2026-116606 changed from “Yes, administrative access” to “No (Administrative UI Access Required)”. Authentication isn’t needed, but the attacker must be able to reach the admin UI. Whether the admin interface is exposed therefore decides how reachable the chain is.

Barracuda CVE-2026-116606 and CVE-2026-111560 at a glance

CVE-2026-116606 Pre-authentication authorization bypass (CWE-288); ESG only; CVSS 4.0 score 9.3; Barracuda severity High; no authentication, admin UI access required
CVE-2026-111560 OS command injection in the timezone field (CWE-78); ESG, ADC, BMA, WCC, WAF, WSG; CVSS 4.0 score 8.6; administrator access required
Exploitation Activity affecting a small number of organizations (Barracuda, November 9, 2026)
CISA KEV Both added 2026-11-10; federal due date 2026-11-13; forensic triage required
Indicators None published by Barracuda

Affected products and patches

Barracuda’s advisory lists a patch ID per product rather than a fixed firmware number. The affected version ranges come from the CVE records.

ProductCVE-2026-116606CVE-2026-111560Barracuda patchAffected per CVE record
Email Security Gateway (ESG)YesYesBNSF-40425 (9.4.017+), BNSF-40430 (below 9.4.017)116606: earlier than 9.4.0.030; 111560: 9.4.0.27 and earlier
Load Balancer ADCNoYesBNADC-165866.4.0 and earlier
Message Archiver (BMA)NoYesBNMA-324685.5.4.0 and earlier
WAF Control Center (WCC)NoYesBNWF-600602.2.1 and earlier
Web Application Firewall (WAF)NoYesBNADC-1658611.0.1 and earlier
Web Security Gateway (WSG)NoYesBNYF-2478916.1.100.100 and earlier

The WAF row lists the same patch ID as ADC, BNADC-16586. Barracuda’s table shows it that way. For both CVEs, Barracuda’s remediation line is to upgrade to the latest firmware version.

Patch and lock down the admin interface

Barracuda’s advisory gives four pieces of guidance:

  1. Confirm the firmware and patch on every device. Barracuda says the device shows the latest firmware version available. Make sure it’s running that version and has the patch for your product from the table above.
  2. Apply the patch by hand if it isn’t there. If a patch hasn’t been applied automatically, Barracuda says to apply it manually as soon as possible. If you’ve turned off automatic patching, Barracuda recommends turning it back on. Barracuda Campus has the steps for manual patching and firmware updates.
  3. Plan for more than one update on old firmware. If a device is several versions behind, Barracuda says you may need more than one update, and to contact Barracuda Support if you need help.
  4. Restrict the admin UI. Barracuda says organizations whose admin interfaces aren’t publicly accessible from the internet are less exposed, and recommends limiting admin access to trusted internal networks with network access controls.

Check exposed appliances for compromise

Barracuda hasn’t published indicators of compromise. CISA set the forensic triage flag on both KEV entries, which ties federal agencies to CISA’s forensics triage requirements on top of patching. Without vendor IOCs, these checks follow from how the bugs work, so treat them as a starting point rather than a vendor checklist:

  • Admin UI exposure. Check firewall rules and run an external scan to find out whether any device’s admin interface was reachable from the internet while unpatched. Those are the devices to look at first.
  • Configuration changes on ESG. CVE-2026-116606 restores a crafted backup archive and changes global configuration. Look for configuration imports or restores, and global settings changes, that nobody on your team made.
  • The timezone setting. CVE-2026-111560 is triggered through the timezone field. A timezone value containing shell characters is a red flag on any of the six products.
  • Admin accounts and sessions. Because CVE-2026-111560 needs administrator access on its own, review admin logins on ADC, WAF, WSG, BMA and WCC for unknown sources.

If anything turns up, treat the device as compromised and contact Barracuda Support, rather than only patching it.

Barracuda CVE-2026-116606 and CVE-2026-111560 response checklist

  • Every ESG, ADC, WAF, WSG, BMA and WCC inventoried with its firmware version
  • Correct patch applied: ESG BNSF-40425 or BNSF-40430, ADC and WAF BNADC-16586, BMA BNMA-32468, WCC BNWF-60060, WSG BNYF-24789
  • Firmware updated to the latest version shown on the device, in several steps if needed
  • Automatic patching turned back on where it was off
  • Admin UI reachable only from trusted internal networks
  • Exposed devices reviewed for unexpected configuration restores and odd timezone values

Timeline

  • October 15 and 22, 2026: Mandiant’s advisories list CVE-2026-111560 (October 15) and CVE-2026-116606 (October 22) as reported by Barracuda.
  • November 2: Barracuda advisory, Mandiant advisories MNDT-2026-0041 and MNDT-2026-0042, and both CVE records published.
  • November 5: Barracuda corrects CVE-2026-116606 to “No (Administrative UI Access Required)”.
  • November 9: Barracuda adds the note about exploitation activity.
  • November 10: CISA adds both CVEs to KEV, with a federal due date of November 13.

What to do now

Check every Barracuda ESG first, since it’s the product exposed to the unauthenticated chain, and confirm BNSF-40425 or BNSF-40430 is applied and the firmware is current. Then patch ADC, WAF, WSG, BMA and WCC for CVE-2026-111560. Take the admin UI off the internet on all of them, and review any device whose admin UI was exposed while unpatched for configuration restores and odd timezone values. For other exploited perimeter flaws, see our posts on Ivanti Connect Secure CVE-2026-104935 and Check Point CVE-2026-123039.

Frequently asked questions

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

Yes. Barracuda's advisory, updated November 9, 2026, says 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.

Does CVE-2026-116606 need authentication?

No. Barracuda corrected the advisory on November 5 to say authentication isn't required, but the attacker must be able to reach the administrative user interface. The bug lets them restore a crafted backup archive and change the ESG's global configuration.

Which Barracuda products are affected?

CVE-2026-116606 affects only the Email Security Gateway. CVE-2026-111560 affects ESG, Load Balancer ADC, Web Application Firewall, Web Security Gateway, Message Archiver and WAF Control Center.

Which Barracuda patch do I need?

Barracuda lists BNSF-40425 for ESG 9.4.017 and later, BNSF-40430 for ESG below 9.4.017, BNADC-16586 for ADC and WAF, BNMA-32468 for Message Archiver, BNWF-60060 for WAF Control Center and BNYF-24789 for Web Security Gateway. It also says to run the latest firmware.

How do I reduce exposure to the Barracuda chain?

Apply the patch and latest firmware, turn automatic patching back on if it was off, and restrict the admin interface to trusted internal networks. Barracuda says organizations whose admin interfaces aren't publicly accessible from the internet are less exposed.

Sources & further reading

Official vendor documentation referenced while writing this guide.

MG

MCSA Guru Team

IT & Systems Administration

We are working IT pros and system administrators who spend our days in Windows Server, Microsoft 365, and the wider Microsoft stack. MCSA Guru is where we write down the fixes and walkthroughs we wish we had found the first time.

MCSA Guru provides independent, educational IT guidance. Microsoft, Windows, Windows Server, Microsoft 365, Exchange, and Microsoft Teams are trademarks of Microsoft Corporation; Docker is a trademark of Docker, Inc. MCSA Guru is not affiliated with or endorsed by Microsoft or Docker. Always test changes in a safe environment before applying them in production.

Related guides

Fixing something right now?

Jump straight into the guide library or search for the exact error or task you are dealing with.