Yaamlabs

Vulnerabilities

Barracuda ESG flaw chain now under active attack

The pre-auth root chain on Barracuda's Email Security Gateway is being exploited and is now in CISA's KEV catalog. How to patch, hunt and recover.

Two Barracuda flaws that together hand an attacker root on the Email Security Gateway (ESG), the appliance that filters a company's inbound and outbound mail, are now being used in real attacks. On November 9 Barracuda said it had found exploitation affecting a small number of organizations. CISA, the US Cybersecurity and Infrastructure Security Agency, added both bugs to its Known Exploited Vulnerabilities (KEV) catalog on November 10 and set a federal fix deadline of November 13.

The flaws are CVE-2026-116606 and CVE-2026-111560, the same pair Barracuda patched on November 2. When the fix shipped there were no reports of attacks, and that changed within a week. The patch has now been out long enough that an exposed appliance is most likely an unpatched one. If you run an ESG and have not confirmed the update landed, treat the box as a target and read on.

How it works

ESG can export its full settings to a backup archive and import one again, for example after a hardware swap. That import rewrites the whole device configuration, so only a logged-in administrator should be able to run it. CVE-2026-116606 (CVSS, the Common Vulnerability Scoring System, rates it 9.3) is an authorization bypass: the import path is reachable without the login it assumes. Mandiant, which reported the bugs, classes it as CWE-288, a sensitive function reachable through an alternate path. An attacker restores a crafted, compatible backup and changes the global configuration, including fields that a later process trusts.

CVE-2026-111560 (CVSS 8.6) is the second half. The time zone value in the system settings is passed to a shell and run as root, and shell metacharacters such as backticks, semicolons and $( ) are not stripped out (CWE-78, operating system command injection). On its own this flaw needs administrator access, which is how Barracuda rates it. Chained behind the first flaw that requirement falls away: the bypass plants a malicious time zone string through the configuration import, and the appliance runs it as root with no account needed. The combined result is unauthenticated root command execution on the device.

An email gateway reads every message going in and out of an organization and sits where the internal network meets the internet, so root on one is a strong foothold. From there an attacker can read mail, redirect where it routes, harvest the credentials the appliance keeps for mail and directory systems, and hold a quiet position inside the network.

The sources disagree on one detail. Barracuda's advisory labels the ESG flaw as requiring administrative access, while its later clarification and Mandiant both describe the bypass as needing no login, only the ability to reach the admin web interface. Both agree the admin interface is the entry point. Mandiant's affected range for the bypass is ESG before version 9.4.0.030.

What attackers are doing

Barracuda posted the exploitation notice on the evening of November 9. The wording is narrow: exploitation activity affecting a small number of organizations. No public indicators of compromise or proof-of-concept exploit went out with the notice, and Barracuda has not named the group behind the attacks or described what they did after reaching root.

CISA followed on November 10, adding both CVEs to the KEV catalog with a due date of November 13 for federal civilian agencies. Three days is a short window by CISA's usual standards, and it reflects a flaw already in use rather than a theoretical one. Both catalog entries call for forensic triage, not patching alone.

The product's record is the reason to move quickly even if you are not a federal agency. In 2023 a China-linked group that Mandiant tracks as UNC4841 exploited a different ESG command injection, CVE-2023-2868, for roughly eight months before it was caught, and Barracuda ended up telling many affected customers to replace the hardware rather than trust a cleanup. A root-level chain on the same appliance is the kind of target that history says gets used more widely once it is public.

What to do

Patch now

Apply the fix for your firmware line. For ESG the patches are BNSF-40425 on builds 9.4.017 and later, and BNSF-40430 on builds below that. Mandiant's records give 9.4.0.030 as the first ESG release without the bypass, and some write-ups cite that version string, so confirm the exact build against Barracuda's advisory rather than this post, since the sources differ on the strings. The command injection also reaches Load Balancer ADC (Application Delivery Controller; patch BNADC-16586), Web Application Firewall (WAF, the filter that screens web traffic), WAF Control Center, Web Security Gateway and Message Archiver, so patch those as well: the bug runs as root there too wherever an admin account can be reached. Barracuda applies these patches automatically by default, but check each device instead of assuming, turn automatic patching back on if it was disabled, and plan for more than one update on firmware that is several versions behind.

If you cannot patch today

Restrict the appliance's administrative web interface to a management network or a short list of admin workstations, enforced on the upstream firewall rather than on the appliance itself. That cuts down who can reach the import path. Anyone already on an allowed network can still run the whole chain, so treat this as a holding measure until the patch is confirmed, not a substitute for it.

Hunt for compromise since early November

The exploitation window opened around November 9 and may reach back to whenever your appliance was first exposed, so check whether you were already hit rather than assuming the patch closes the matter. Look for:

  • Configuration changes or backup-restore activity you cannot tie to a change ticket, imports in particular.
  • Admin accounts that are new or modified, and allowed admin IP ranges, mail routing or relay settings that differ from a backup taken before November 2.
  • Time zone values that are anything other than a plain zone name such as Europe/London; backticks, semicolons, pipes or $( point to an injection attempt.
  • Root-level processes, cron jobs or scripts you did not create, and outbound connections from the appliance you cannot account for.

Preserve and export the appliance logs before you reboot or reset anything. A restart can wipe the evidence responders need, and the KEV entries ask federal teams to triage for exactly this reason.

If the box may have been rooted

Treat a rooted email gateway as a compromise of all the mail it handled. Follow Barracuda's incident guidance, rotate every credential and secret the appliance held, and open a support case with Barracuda. That rotation covers admin passwords, the LDAP or Active Directory bind account, SMTP relay credentials, API keys and the TLS private keys stored on the device. Given how deeply UNC4841 embedded itself in ESG appliances in 2023, be ready for the recommendation to replace a device that was genuinely breached rather than reimage it.

Working out which appliance admin interfaces can be reached from untrusted networks is where our attack surface management work begins, and our security operations team runs the log review and hunting described above. Open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.


Sources: Barracuda security advisory, CISA KEV catalog, Rescana, Suped, eSecurity Planet, Mandiant MNDT-2026-0041, Mandiant MNDT-2026-0042.

Back to the blog, or read this post on the full site.