Barracuda ESG root chain exploited a week after the patch
Two Barracuda flaws that combine to give unauthenticated root on the Email Security Gateway were patched on 2 November, analysed publicly on 5 November and confirmed exploited by 9 November. The vulnerable function is configuration restore, the same path the 2023 UNC4841 campaign used for persistence.
Barracuda’s Email Security Gateway has again gone from patch to confirmed exploitation in about a week. On 2 November Barracuda fixed two flaws that, chained, give an attacker who can reach the administrative interface root on the appliance without logging in [1]. On 5 November watchTowr Labs published a patch-diff analysis of the chain [2]. By 9 November Barracuda had added a line to its advisory: “We have identified exploitation activity affecting a small number of organizations” [1]. CISA added both CVEs to the Known Exploited Vulnerabilities catalogue on 10 November with a three-day federal deadline of 13 November [10]. For an appliance that sits in the mail path and was the entry point for a persistent espionage campaign in 2023, that is a short window [4].
The chain
CVE-2026-116606 is a pre-authentication authorisation bypass that affects the ESG only. Barracuda scores it 9.3 under CVSS 4.0 and requires that the attacker can reach the admin UI [1]. watchTowr traces the root cause to request handling: a failed password-change attempt did not end the request but dropped to a low-privilege role, and processing continued [2]. The reachable function is configuration restore. The CVE record, as quoted by Daily CyberSecurity, says an unauthenticated attacker can “restore a crafted, compatible backup archive” [9]. Two outlets that walked the chain report that backup integrity relied on a fixed, hard-coded secret, so forged archives pass the check [8][9].
CVE-2026-111560 is an OS command injection, scored 8.6, in the timezone setting [1]. The value reached a shell command, and the helper script runs through sudo, so injected commands execute as root [2]. It affects six products: ESG, Load Balancer ADC, Message Archiver, WAF Control Center, Web Application Firewall and Web Security Gateway [1]. Outside the ESG it still needs administrative access, because the bypass is ESG-only [6][9]. Barracuda’s patch now ends the request on a failed password change, validates timezone values against real zone files and removes the shell call [2].
What the record says, and where it disagrees
- Timeline. Barracuda received the injection report on 15 October and the bypass report on 22 October, according to Mandiant’s CVE records as summarised by SecurityWeek and ThreatDefence [6][7]. Patches and the advisory followed on 2 November [1]. Field Effect, SecurityWeek and Cyber Kendra all reported no known exploitation between 3 and 6 November [11][6][8]. Exploitation was added to the advisory on 9 November, and the Canadian Cyber Centre updated its own notice the same day, citing open-source reporting rather than its own confirmation [1][3].
- Fixed build. Sources differ. watchTowr compared vulnerable 9.4.0.027 with patched 9.4.0.029, and GBHackers repeats 9.4.0.029 as the fix [2][14]. The CVE record, SecurityWeek, the Canadian Cyber Centre and Field Effect put the line at 9.4.0.030 [6][3][11]. Cyber Kendra and ThreatDefence both recommend treating 9.4.0.030 as the target [8][7].
- Authentication. Barracuda first wrote that exploitation “requires an attacker to have access to the administrative interface”. On 6 November it clarified that admin-level privileges are not needed [5]. Its advisory now reads, in effect, no authentication but admin UI reachability required [7].
- Severity. Barracuda labels the bypass High; the CNA score is 9.3 Critical [8]. watchTowr notes a patch comment citing 9.8 [2].
- Public code. watchTowr’s post links a detection artefact generator for checking susceptibility [2]. Daily CyberSecurity describes the release as proof-of-concept exploit code and dates it 3 November, two days before the post itself is dated [9]. KEV restatements also describe watchTowr as having published exploit code [10].
Barracuda has not said who is exploiting the chain, how many organisations are affected or what was done after access [1][9]. No public source links the activity to any actor. Exposure counts for internet-reachable ESG admin interfaces have not been published by any of the sources reviewed [5][7].
Why the configuration restore path matters
The 2023 campaign is the relevant precedent. Mandiant assessed with high confidence that UNC4841 conducted espionage in support of the People’s Republic of China after exploiting CVE-2023-2868 [4]. After Barracuda’s remediation, Mandiant found UNC4841 had prepared for it. One backdoor, DEPTHCHARGE, was able to re-infect a clean appliance through a restored configuration [4]. Mandiant’s guidance was to replace compromised appliances, not clean them, and to rotate credentials, because the configuration database could hold plaintext passwords [4].
The new bypass lands on the same function. An attacker who can restore an arbitrary configuration can change the appliance’s global settings before any command injection is used [6]. That means a patched appliance is not automatically a trusted appliance. Any configuration restored or exported since mid-October should be treated as untrusted until it has been compared with a known-good copy [7].
The pattern is also broader than Barracuda. CISA’s 9 November additions for GPUStack, FreeSWITCH, OpenSSH on some musl-based systems, and IBM Aspera Faspex carried a three-day deadline under BOD 26-04, which also requires forensic triage [13]. Dustin Childs of TrendAI’s Zero Day Initiative told CyberScoop that fewer exploited zero-days “does not mean we’re seeing less exploitation in the wild”, and attributed part of the shift to AI being better at reversing patches than at finding bugs in closed-source code [12]. Defenders should plan on public patch analysis arriving within days of a fix.
What to do
- Inventory every Barracuda ESG, ADC, WAF, WSG, BMA and WCC instance, including those managed by service providers [1][7].
- Confirm the ESG is on 9.4.0.030 or later with BNSF-40425 or BNSF-40430 applied, and apply the product-specific patches elsewhere. Older firmware may need several upgrade steps [1][11].
- Restrict the admin interface to management networks or VPN and set the administrator IP range. Barracuda notes devices without internet-exposed admin interfaces face less exposure [1][7].
- Re-enable automatic patch receipt where it was turned off, and apply missed patches manually [1].
- Hunt from 15 October onward. Use web, proxy and firewall logs in front of the appliance and ESG web syslog. Look for failed password-change events from outside management ranges, unscheduled configuration restores, configuration changes without a preceding login, timezone values containing shell metacharacters and unexpected outbound traffic from the appliance [7].
- If compromise is suspected, preserve state, compare the configuration with a pre-15 October backup, contact Barracuda support and rotate every credential and key the appliance held. Given 2023, consider replacement rather than in-place clean-up [7][4].
The offensive security read
This is a patch-diff story. The bugs were found and reported privately, fixed within three weeks, and analysed in public three days after release [6][2]. Exploitation was confirmed four days later [1]. The chain does not need a novel primitive. It needs a request handler that keeps going after an error, a backup format that trusts a fixed secret and a configuration field that reaches a root shell [2][9]. Email security gateways hold mail flow, directory credentials and a trusted network position, and they rarely run endpoint agents [4][7]. For practitioners, the measure that matters is how quickly an organisation can patch and verify its edge appliances after a fix, before public analysis arrives.
Sources
Every R3KONX article cites its primary material. 14 sources, in order of first citation. Links open the original publication.
- Pre-Authentication Authorization Bypass and Command Injection Vulnerabilities in Certain Barracuda Products Barracuda Networks Trust Center · 2026-11-02
- Barracuda Networks is your new best friend (Barracuda Email Security Gateway Pre-Auth Remote Root RCE CVE-2026-116606 / CVE-2026-111560) watchTowr Labs · 2026-11-05
- Barracuda Networks security advisory (AV26-1112) - Update 1 Canadian Centre for Cyber Security · 2026-11-09
- Diving Deep into UNC4841 Operations Following Barracuda ESG Zero-Day Remediation (CVE-2023-2868) Mandiant / Google Cloud Threat Intelligence · 2023-08-29
- Barracuda warns of critical flaws allowing root access to devices BleepingComputer · 2026-11-03
- Barracuda Email Security Gateway authentication bypass opens path to root SecurityWeek · 2026-11-04
- CVE-2026-116606 Barracuda ESG: Patching and Threat Hunting ThreatDefence · 2026-11-09
- CVE-2026-116606: Barracuda ESG Bug Chain Gives Root Access Cyber Kendra · 2026-11-06
- Barracuda ESG Vulnerability Chain Exploited in the Wild After PoC Exploit Release Daily CyberSecurity (securityonline.info) · 2026-11-10
- CISA Adds Six Exploited Flaws in Outlook, Chrome, Barracuda, Cisco and Openwave to KEV Catalog Daily CyberSecurity (securityonline.info) · 2026-11-10
- Barracuda ESG flaws could give attackers root access Field Effect · 2026-11-03
- Microsoft fixes over 1,000 vulnerabilities in November Patch Tuesday CyberScoop · 2026-11-10
- CISA Adds 4 Exploited Flaws to KEV: Nov. 12 Deadline eSecurity Planet · 2026-11-09
- Barracuda Email Security Gateway Flaws Allow Unauthenticated Attackers to Execute Commands as Root GBHackers · 2026-11-10
Researched and written by the R3KONX Analysis Desk from the primary material cited below. CISA's catalogue could not be retrieved directly, so KEV dates and deadlines are taken from published restatements, and exploitation details rest on Barracuda's one-line confirmation. Corrections: event@r3konx.asia.
