CVE-2026-116606 - Barracuda Networks Email Security Gateway (ESG) Authentication Bypass Using an Alternate Path or Channel Vulnerability

CVE-2026-116606

Barracuda ESG - Pre-Auth Config Import via a Password Change That Fails but Keeps Going

What is Barracuda Email Security Gateway?

The Barracuda Email Security Gateway, usually shortened to ESG, is an email security appliance sold as hardware, a virtual machine, and a cloud image. It sits in front of an organization's mail infrastructure and inspects inbound and outbound SMTP traffic for spam, phishing, malware, and data leakage before messages reach Exchange, Microsoft 365, or another mail store. Administrators manage it through a web console that also handles firmware updates, clustering, and configuration backup and restore.

That position makes an ESG an unusually attractive target. It terminates and reads the organization's mail in cleartext, it holds quarantined message bodies and attachments, and it usually holds directory credentials used for recipient verification and LDAP lookups. It is also by design reachable from the internet on the mail path, and in many deployments its administration interface is reachable too. Barracuda's ESG line has a history here: in 2022 and 2023 the espionage group tracked as UNC4841 exploited CVE-2023-2868 as a zero-day against these same appliances, and Barracuda ultimately told affected customers to replace the hardware rather than patch it.

Overview

CVE-2026-116606 is a pre-authentication authorization bypass in the ESG administration interface. According to watchTowr Labs, which published the public analysis, the flaw lives in the password change logic: when a password change fails, the appliance reports an error but continues processing the request and leaves the caller holding a low-privilege role rather than no role at all. That partial session is enough to reach the appliance's configuration import function.

From there the attacker restores a crafted configuration backup archive and rewrites the appliance's global configuration. Backups are protected by a checksum, but the secret used to compute that checksum is hardcoded in the product, so an attacker can forge an archive that the appliance accepts as genuine. Mandiant, the CNA for this CVE, scores it 9.3 Critical under CVSS 4.0 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N). NVD has since published its own score of 9.8 Critical under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), which is the rating shown in the severity badge above. Both put it at the top of the Critical band.

The bypass matters most as step one of a chain. A restored backup can set the appliance timezone, and CVE-2026-111560 turns that timezone value into root command execution. Together they take an unauthenticated attacker who can reach the admin interface all the way to root on the appliance. Barracuda confirmed on 2026-11-09 that it had identified exploitation activity affecting a small number of organizations, and CISA added both CVEs to the KEV catalog on 2026-11-10 with an unusually short three-day remediation deadline of 2026-11-13.

Affected Versions

Product Vulnerable Fixed
Barracuda Email Security Gateway (ESG) Earlier than 9.4.0.030 9.4.0.030 or later
ESG running 9.4.017 or later Unpatched Security patch BNSF-40425
ESG running earlier than 9.4.017 Unpatched Security patch BNSF-40430

Sources disagree slightly on the boundary. Mandiant's advisory lists everything earlier than 9.4.0.030 as affected, while Barracuda's own documentation has been reported as treating 9.4.0.029 as already patched. Treat 9.4.0.030 as the target. No other Barracuda product is affected by this CVE; the companion command injection reaches five more.

Technical Details

The weakness is CWE-288, authentication bypass using an alternate path or channel. In plain words, the appliance has a front door that checks credentials and a side route that does not, and the side route reaches the same functionality. Here the side route is created by error handling that fails open: the password change routine detects the failure, emits an error, and then carries on down the same code path a successful change would have taken, assigning a role in the process.

The second half of the problem is trust in the backup archive. A configuration backup is attacker-supplied input, and the only thing standing between a forged archive and a full configuration rewrite is a checksum computed with a secret that ships inside the product. A hardcoded secret is not a secret once anyone has a copy of the firmware, so the integrity check is decorative.

The attack is network-reachable, needs no credentials and no user interaction, and the entry point is a request sequence against the administration interface rather than the mail path. Complexity is low and the whole chain is automatable. The one real precondition is reachability: Barracuda notes that organizations whose administration interfaces are not exposed to the internet face materially less risk from this.

Discovery

Mandiant is the CVE Numbering Authority for both CVEs and published advisory MNDT-2026-0042 on 2026-11-02. Its disclosure timeline records the authentication bypass as reported to Barracuda on 2026-10-22, one week after the companion command injection. Neither Mandiant nor Barracuda has named an individual researcher; Mandiant's advisory credits the report to Barracuda itself.

The public technical detail comes from watchTowr Labs, which reverse-engineered the patch, worked out the password change and backup restore path, and demonstrated the chain by writing a file to an appliance as root. watchTowr released what it calls a detection artifact generator rather than a weaponized exploit, though the script accepts an arbitrary operator-supplied command. Reports place that publication between 2026-11-03 and 2026-11-05; the later date is the better corroborated of the two.

Exploitation Context

Barracuda updated its Trust Center advisory on 2026-11-09 to say it had identified exploitation activity affecting a small number of organizations. The company has not said which of the two CVEs was used, whether the pair was chained in the observed attacks, or published indicators of compromise, and no threat actor has been named. CISA's KEV entry does not flag known ransomware use.

The sequence is worth noting because it is a common one. Patches and advisories landed on 2026-11-02 with no reported exploitation. Public analysis and a usable tool followed within days. Confirmed exploitation arrived on 2026-11-09, roughly a week after the patch and only a few days after the research went public. The three-day KEV deadline reflects that compression.

No exposure census from Shadowserver, Censys, or GreyNoise had been published for this CVE as of 2026-11-10, and neither Barracuda nor CISA has given a victim count. The relevant population is not all ESG appliances but those with an internet-reachable administration interface, which is a smaller and unmeasured subset.

Remediation

  1. Upgrade ESG firmware to 9.4.0.030 or later. This single upgrade addresses both CVE-2026-116606 and CVE-2026-111560.
  2. Confirm the security patch applied as well as the firmware version: BNSF-40425 for appliances on 9.4.017 or later, BNSF-40430 for appliances on earlier builds. A firmware number alone is not proof the patch landed.
  3. Re-enable automatic security patching if it was turned off. Barracuda calls this out specifically, because a number of appliances in the field had it disabled.
  4. Restrict the administration interface to trusted internal networks or a management VLAN, and keep it off the public internet. This does not fix the bug but it removes the attack surface, and it is the only meaningful control for an appliance that cannot be patched immediately.
  5. Treat any internet-exposed, unpatched appliance as potentially compromised. Because the chain ends in root, an upgrade does not evict an attacker who already arrived. Review the running configuration against a known-good backup for unexplained changes, check the timezone setting in particular, look for unexpected accounts and SSH keys, and inspect cron and startup scripts.
  6. Review administration interface logs for configuration import or restore events nobody initiated, for failed password change attempts followed by privileged actions, and for access from unfamiliar addresses. Look back to at least 2026-11-02 and preferably to 2026-10-22. Preserve logs and appliance state before remediating, in line with CISA's Forensics Triage Requirements under BOD 26-04.
  7. Federal civilian agencies must remediate or discontinue use by 2026-11-13. With confirmed exploitation, public analysis, and a tool in circulation, every other operator should treat that date as the outer limit rather than a target.

Key Details

PropertyValue
CVE ID CVE-2026-116606
Vendor / Product Barracuda Networks - Barracuda Email Security Gateway (ESG)
NVD Published2026-11-02
NVD Last Modified2026-11-12
CVSS 3.1 Score9.8
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
SeverityCRITICAL
CWE CWE-288 find similar ↗
CISA KEV Added2026-11-10
CISA KEV Deadline2026-11-13
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

CISA BOD 26-04 Deadline: 2026-11-13. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA's "Forensics Triage Requirements" (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Timeline

DateEvent
2026-10-22Barracuda receives the authentication bypass report (per Mandiant's disclosure timeline)
2026-11-02Barracuda publishes its Trust Center advisory and ships patches; CVE published alongside Mandiant advisory MNDT-2026-0042
2026-11-05watchTowr Labs publishes a technical analysis of the full pre-auth to root chain plus a detection artifact generator
2026-11-09Barracuda updates the advisory to confirm exploitation activity affecting a small number of organizations
2026-11-10Added to CISA Known Exploited Vulnerabilities catalog
2026-11-12NVD publishes a CVSS 3.1 base score of 9.8 (Critical)
2026-11-13CISA BOD 26-04 remediation deadline