CISA lists Barracuda ESG authentication bypass CVE-2026-116606 as exploited
Barracuda Email Security Gateway before 9.4.0.030 lets an unauthenticated remote attacker import a crafted configuration backup; CISA now lists the flaw as exploited.
What CISA added
On 2026-11-10 CISA added CVE-2026-116606 to its KEV catalog of known exploited vulnerabilities. The entry is named “Barracuda Networks Email Security Gateway (ESG) Authentication Bypass Using an Alternate Path or Channel Vulnerability” and is classed as CWE-288. Known ransomware campaign use is listed as Unknown. For US federal civilian agencies bound by BOD 22-01, the due date is 2026-11-13, three days after the listing.
The same day CISA also listed CVE-2026-111560, an OS command injection in several Barracuda appliance products. The KEV entry for CVE-2026-116606 says plainly that it “can be chained with CVE-2026-111560”, and both records point to the same Barracuda security advisory.
What the flaw does
According to the NVD description, published on 2026-11-02 and still in the status Undergoing Analysis, the bug is an authentication bypass in Barracuda Email Security Gateway versions earlier than 9.4.0.030. It allows an unauthenticated remote attacker to invoke a configuration-import function and restore a crafted, compatible backup archive. The result is unauthorized modification of the appliance’s global configuration.
CWE-288 covers authentication bypass using an alternate path or channel: the login check exists, but some route to a protected function does not pass through it. Here that route reaches the configuration import. An attacker who can restore a configuration does not need to guess a password, because the appliance accepts the attacker’s settings as its own.
Why the chain matters
On its own, CVE-2026-111560 requires an authenticated administrator: shell metacharacters in the timezone configuration field are not neutralized, and the injected commands execute with root privileges when the crafted timezone value is later processed. CVE-2026-116606 removes the need for that login, since it lets an outside party change the global configuration without authenticating. The records do not walk through the chain step by step, but read together they describe a path from no credentials to configuration control, and from configuration control to commands running as root.
Severity
The CVSS score in the NVD record is a secondary CVSS 4.0 score of 9.3 CRITICAL, with the vector 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. That means a network attack vector, low attack complexity, no attack requirements, no privileges required and no user interaction, with high impact on confidentiality, integrity and availability of the vulnerable system and no impact on subsequent systems. The KEV listing adds that the flaw is already being exploited.
The references in the record are the Barracuda advisory on the trust.barracuda.com site, the Mandiant disclosure MNDT-2026-0042 in the mandiant/Vulnerability-Disclosures repository on GitHub, and the KEV catalog entry.
What to do
The KEV required action is to apply mitigations in accordance with vendor instructions, following CISA’s BOD 26-04 guidance on prioritizing security updates based on risk and its “Forensics Triage Requirements”, and to discontinue use of the product if mitigations are unavailable. Stakeholders are also asked to evaluate each asset’s internet exposure.
The affected range in NVD ends before 9.4.0.030, so operators should confirm that every Email Security Gateway runs that version or later, using the Barracuda advisory for the exact steps. Because the bypass rewrites the global configuration, patching alone does not show whether an appliance was already touched. Comparing the current configuration with a known good backup, and checking the timezone setting for unexpected characters given the chained CVE-2026-111560, are sensible parts of the forensic triage that CISA asks for.
Source: CVE-2026-116606 (NVD, CISA KEV)