Barracuda ESG CVE-2026-116606: no login needed, Barracuda now says, but the admin interface must be reachable
Barracuda changed its advisory on 5 November: CVE-2026-116606 in its Email Security Gateway needs no authentication, only a reachable administrative interface, which matches the CVE record's unauthenticated remote attacker. The CVE record gives 9.4.0.030 as the fixed boundary. On 9 November Barracuda added that it has seen exploitation against a small number of organizations; CISA added both CVEs to its exploited catalogue on 10 November, due 13 November.
By Parminder Kumar Sharma · LinkedIn · · 20 min read
Update, 11 November 2026: CISA has added both Barracuda CVEs to its exploited catalogue
CISA's Known Exploited Vulnerabilities catalogue, release 2026.11.10 (released at 19:03 GMT on 10 November, 1,779 entries, read on 11 November), now lists both CVE-2026-116606 and CVE-2026-111560. Both entries are dated 10 November, carry a due date of 13 November, and show the field Forensic Triage: Yes. Known ransomware campaign use is "Unknown" for both. The release came about 17 hours after the time of Barracuda's notice, 02:00 GMT on 10 November (derived), and 8 days after the CVE records were published on 2 November (derived, by date). The earlier lines in this article that say CISA's catalogue listed neither CVE describe the releases of 30 October and 9 November, which came before.
What the catalogue prints. For CVE-2026-116606 its short description says the gateway "contains an authentication bypass using an alternate path or channel that could allow an unauthenticated remote attacker to invoke a configuration-import function and restore a crafted, compatible backup archive, resulting in unauthorized modification of the appliance's global configuration", and that it "can be chained with CVE-2026-111560". For CVE-2026-111560 it prints an OS command injection that "could allow an authenticated administrator to inject OS commands that execute with root privileges when the crafted timezone value is subsequently processed". Its product line for that entry names seven families: Email Security Gateway, Load Balancer, Application Delivery Controller, Message Archiver, WAF Control Center, Web Application Firewall and Web Security Gateway. The CVE record for CVE-2026-111560, read earlier, lists the Email Security Gateway and five other products, so the two lists are not the same count, and this article's scope remains the gateway. The catalogue notes link Barracuda's advisory page and the two Mandiant advisory files.
What the CVE records now read. Both records show a last update of 04:55 GMT on 11 November. Each carries CISA's enrichment entry, still stamped 2 November, which now reads Exploitation: active (it read none when this article was updated on 10 November), and a catalogue entry dated 10 November. The same entries print Automatable: yes and Technical Impact: total for CVE-2026-116606, and Automatable: no and Technical Impact: total for CVE-2026-111560. The records do not say when the value changed.
What is still not stated. Which CVE was used, or both chained; when exploitation began; how many organizations "a small number" means; what evidence CISA relied on; any indicator. Barracuda's own page was last read on 10 November and was not read again for this update. The catalogue listing is a government statement that the flaws are exploited; it adds no detail about how, where or by whom.
What changed in this article: the standfirst, a sentence of the 10 November update, the exploitation paragraph, the key facts line, the last checklist item and the title of the catalogue source now say what was read on each date. The earlier readings are kept as they were. CISA's due date gives federal agencies three days (derived); the ranked checklist below is unchanged and now carries more weight.
Update, 10 November 2026 about 15:00 GMT: Barracuda now says it has seen exploitation, against a small number of organizations
Barracuda has added a statement about exploitation. This article was written on 2 November and updated on 7 November, and both said that no source read reported exploitation. That is no longer true of Barracuda's own page. A notice at the top of the advisory now reads: "Updated November 9, 2026, at 9:00pm EST: We added information about exploitation activity that has been observed affecting a small number of organizations." The overview paragraph now says: "We have identified exploitation activity affecting a small number of organizations." This site read the page on 10 November at about 12:41 GMT in a browser, because the page is built with JavaScript. 9:00pm EST on 9 November is 02:00 GMT on 10 November, which is 7 days 13 hours after the CVE records were published at 12:59 GMT on 2 November (derived).
What the text read does not say: which CVE was used (CVE-2026-116606, CVE-2026-111560 or the two chained), when exploitation began, how many organizations "a small number" means, which products or builds were hit, how access was gained, or any indicator. The advisory table still shows "Advisory Updated: November 2, 2026" for both CVEs, so that field does not follow the notice, as it did not follow the 5 November change.
What others say. CISA's Known Exploited Vulnerabilities catalogue, release 2026.11.09 (released 19:54 GMT on 9 November, 1,773 entries, read on 10 November), lists neither CVE. That release is earlier than Barracuda's notice (derived), so its silence says only that CISA had not listed them yet. When read on 10 November, both CVE records had been last updated on 3 November and carried CISA's enrichment dated 2 November reading Exploitation none (the 11 November update says what they read later).
What a reader should do (this site's suggestion; Barracuda's page lists no indicators). Treat an ESG whose administrative interface was reachable from untrusted networks while it ran a build earlier than the fix as possibly already affected, not only as exposed. Compare its global configuration with a known good copy, and rotate the credentials and keys that configuration holds. The ranked checklist below, including restricting the administrative interface and updating, is unchanged and now carries more weight.
What changed in this article: the standfirst, the "What none of this establishes" box, the key facts line on exploitation and the sentence in the exploitation section that said Barracuda's page was silent now say what was read on each date. The earlier readings are kept as they were.
Update, 7 November 2026 about 12:15 GMT: Barracuda now says no login is needed for CVE-2026-116606, and watchTowr has published how the two flaws chain to root
This article was written on 2 November, when Barracuda's advisory listed "Authentication Required: Yes, administrative access" for CVE-2026-116606, against a CVE record that says "an unauthenticated remote attacker" can exploit it. That was true of the page then. Read again on 7 November, Barracuda has changed its own field.
What Barracuda's page now says. A notice at the top reads: "Updated November 5, 2026, at 2:30pm EST: The “Authentication Required” field for CVE-2026-116606 has been changed from “Yes, administrative access” to “No (Administrative UI Access Required)”. Authentication is not required to exploit this vulnerability; however, exploitation requires the administrative user interface (Admin UI) to be accessible to the attacker." The advisory's own "Advisory Updated" field still reads 2 November. CVE-2026-111560, the command injection, still lists "Yes (Administrative Access)". So the two readings this article set side by side now agree on the main point: no login is needed for CVE-2026-116606, and what an attacker needs is network reach to the admin interface.
What watchTowr published. On 5 November watchTowr Labs posted an analysis titled "Pre-Auth Remote Root RCE" for CVE-2026-116606 and CVE-2026-111560. It compared Barracuda ESG 9.4.0.027, which it calls vulnerable, with 9.4.0.029, describes a single unauthenticated request that chains the two flaws to root, and shares a detection artefact generator for defenders. That is an outside researcher's demonstration, not a report of attacks, and this site did not run it.
The version question. The CVE record still says "versions earlier than 9.4.0.030", while watchTowr treats 9.4.0.029 as the build that carries the fix, and Barracuda's advisory says only "Upgrade to the latest firmware version". This site has not settled which build first carries the fix; the latest firmware satisfies every reading.
What has not changed. CISA's enrichment on the CVE record, dated 2 November, says Exploitation none, Automatable yes and Technical Impact total, and neither CVE is in CISA's Known Exploited Vulnerabilities catalogue, release 2026.11.06. With a public walkthrough now out, the checklist item on restricting the admin interface to trusted networks matters more (this site's suggestion; Barracuda gives the same restriction advice). The title below says Barracuda requires admin access; Barracuda no longer says that for CVE-2026-116606.
Eleven days, then two readings of one flaw
Mandiant's advisory file for CVE-2026-116606 prints 22 October 2026 as the date the flaw was "Reported by Barracuda" and 2 November as the date the CVE was published. That is 11 days (derived). On the day of publication the two pages that matter describe the same flaw in opposite terms. The CVE record, Mandiant's file and the GitHub advisory built from them say an "unauthenticated remote attacker" can invoke a configuration import function on a Barracuda Email Security Gateway (ESG) and restore a crafted backup archive. Barracuda's own page said that exploitation "requires an attacker to have access to the administrative interface" of an affected product and listed "Authentication Required: Yes, administrative access". On 5 November Barracuda changed that field to "No (Administrative UI Access Required)" (see the update at the top).
Both were read between 18:33 and 18:36 GMT on Monday 2 November 2026, within hours of publication. Barracuda titles its page "Pre-Authentication Authorization Bypass and Command Injection Vulnerabilities", so the vendor's own headline says pre-authentication while its own table says authentication is required. This briefing sets the two readings side by side, says what each establishes, and gives a ranked checklist that works whichever reading proves right.
Stated and not stated
What the sources read on 2 November 2026 state about CVE-2026-116606, and what they leave out. Barracuda page, CVE record, Mandiant file, GitHub advisory and NVD record, as named.
| Question | Stated, and by whom | Not stated |
|---|---|---|
| Who can trigger it | CVE record, Mandiant, GitHub: an unauthenticated remote attacker, with Privileges Required: None in the CVSS vector. Barracuda: access to the administrative interface is needed, and Authentication Required: Yes, administrative access. | Whether access means network reach to the interface or a logged in administrator. Which page is right. |
| What it does | CVE record: invoke a configuration import function, restore a crafted, compatible backup archive, resulting in unauthorized modification of the appliance's global configuration. | What compatible requires, where the archive comes from, what the global configuration holds. |
| Code execution or root | Barracuda: if exploited in combination with CVE-2026-111560, an attacker could bypass authorization controls and obtain root access. CVE-2026-111560: an authenticated administrator, timezone field, root. | How the two connect. Whether CVE-2026-116606 alone gives anything beyond configuration change. |
| Affected and fixed | CVE record: ESG earlier than 9.4.0.030. Barracuda: ESG affected, patches BNSF-40425 (9.4.017+) and BNSF-40430 (<9.4.017). | Hardware, virtual or cloud forms. Whether either patch is the 9.4.0.030 build. Barracuda prints no fixed version number for this CVE. |
| Severity | CVE record: CVSS 4.0 score 9.3, CRITICAL, assigned by Mandiant as CNA. Barracuda: CVSS Score 9.3, Severity High. NVD: Awaiting Analysis, with Mandiant's score shown as secondary. | Why Barracuda labels 9.3 as High. |
| Exploitation | KEV 2026.10.30 lists neither CVE. | Any statement from Barracuda or Mandiant, either way. |
| Who found it | Mandiant's file: Reported by Barracuda. Barracuda: has identified. The CVE record gives discovery as UNKNOWN. | An outside finder, if any. |
The first row is the one that changes what a defender does. If the CVE record is right, anything that can reach the interface can attempt the import without credentials. If Barracuda's table is right, an attacker needs more than network reach. Barracuda's own sentence that organisations whose administrative interfaces are not publicly accessible "are less exposed to this attack path" fits both readings, and so does its advice to restrict those interfaces.
The path as the sources state it
The CVE record's description is one sentence: an authentication bypass in ESG versions earlier than 9.4.0.030 "allows an unauthenticated remote attacker to invoke a configuration-import function and restore a crafted, compatible backup archive, resulting in unauthorized modification of the appliance's global configuration." Mandiant's file adds CAPEC-115, Authentication Bypass, and the weakness class CWE-288, Authentication Bypass Using an Alternate Path or Channel. That class means a protected function can be reached by a route that does not apply the usual check. It does not say which route.
Configuration import is a feature name, not a risk description. To an administrator it sounds like housekeeping. The record says what the function becomes in the wrong hands: a way to replace the appliance's global configuration. A mail gateway sits in the path of inbound and outbound mail, so the stakes depend on what that configuration holds. The sources do not list it. Routing, filtering rules, administrator accounts and stored credentials are all plausible contents of a gateway configuration, but that is this site's inference, and no source read confirms any of them.
Compatible is a label for a constraint that is not printed. An archive is restored only if it is compatible, which implies a check on version, format or contents. A defender would like to know whether that check is also a barrier for an attacker, for example whether a valid archive must come from the same appliance. The sources do not say. Treating compatible as reassurance would be the friendly name fallacy applied to an adjective.
Barracuda's chain is stated, its mechanism is not. The vendor's overview says that if CVE-2026-116606 and CVE-2026-111560 are "exploited in combination", an attacker could bypass authorisation and "obtain root access to the device". CVE-2026-111560 is a command injection in the timezone configuration field of certain appliance products using common Barracuda code, requiring an authenticated administrator, scored 8.6 with Privileges Required: High, affecting ESG up to 9.4.0.27. Read together, the bypass supplies the missing authentication and the injection supplies the code execution. That sentence is this site's reading of Barracuda's summary. Neither the CVE record nor Mandiant's file says that a restored configuration reaches the timezone field, and the diagram marks that link as not stated.
Pre-authentication is also a label. Barracuda's page uses it in its title and in the overview, then lists Authentication Required: Yes, administrative access in the advisory block for the same CVE. One reasonable explanation is that the vendor means the flaw is reachable before login but only on the administrative interface. Another is a drafting inconsistency. The page does not say, and the CVE record's Privileges Required: None was assigned by a different party, the CNA. A reader should not choose between them on a guess.
Dates, and the one that is missing
Mandiant's file lists two dates for CVE-2026-116606: 2026-10-22 "Reported by Barracuda" and 2026-11-02 "CVE published and Mandiant advisory released". The CVE record shows the ID was reserved on 26 October, four days after the report date (derived), and published at 12:59:11 GMT on 2 November, seven days after reservation (derived). The companion command injection, CVE-2026-111560, follows the same shape: reported 15 October, reserved 16 October, published at 12:59:03 GMT on 2 November, 18 days after the report date (derived). The CVE records name Mandiant as the CNA, the body that assigned them.
Other postings followed in order: NVD at 13:17 GMT (18 minutes after the CVE record, derived), Barracuda's page at 13:58 GMT (about 59 minutes, derived, from the publication time in its own page data), and the GitHub advisory at 15:31 GMT (152 minutes, derived). Barracuda's page and its table both print the advisory date as 2 November 2026.
The fix date is not printed. Barracuda says it "immediately initiated a comprehensive remediation process and released security patches" and gives no date. Mandiant's file prints no fix date. The gap between the release of a fix and the public write up therefore cannot be computed from these sources, and this briefing does not guess it. What the timeline does show is a coordinated publication: the two CVE records appeared about 8 seconds apart (derived), and the vendor page, the NVD entry and the GitHub advisory followed within about two and a half hours.
Who found the flaw is also thin. "Reported by Barracuda" in Mandiant's file reads as Barracuda reporting to the CNA, and Barracuda's page says it "has identified" the vulnerabilities. The CVE record's discovery field says UNKNOWN. Anyone writing that Mandiant discovered it would be going beyond the record.
The fix, and how Barracuda says it arrives
Remediation as each source states it, read 2 November 2026.
| Source | What it says | Gap |
|---|---|---|
| CVE record, NVD, Mandiant | ESG versions earlier than 9.4.0.030 are affected. Remediation implies 9.4.0.030 or later. | Barracuda's page does not print 9.4.0.030 at all. |
| Barracuda table | ESG: patch BNSF-40425 (9.4.017+), BNSF-40430 (<9.4.017). Remediation: Upgrade to the latest firmware version. | Patch IDs are not tied to 9.4.0.030. Version strings use two formats. |
| Barracuda guidance | Verify the latest firmware and all patches. If a patch was not applied automatically, apply it manually. If automatic patching is off, set devices to receive patches automatically. | How to apply a patch is on Barracuda Campus, which answered with an empty body and was not read. |
| Barracuda guidance | Restrict administrative interfaces to trusted internal networks and use network access controls. | No indicators of compromise and no detection guidance are published. |
Barracuda says the device "will show the latest firmware version available" and that a device several versions behind "may need to perform more than one update". It points customers to Barracuda Support. That is the delivery model the page states: patches pushed automatically where automatic patching is on, and manual application otherwise. The page does not say whether the 9.4.0.030 build is delivered the same way, and it does not say whether virtual or cloud ESG forms follow a different route. Those are questions for Barracuda Support, not for inference.
Exploitation, exposure and earlier ESG history
The CISA catalogue read at 18:33 GMT is version 2026.10.30, released at 17:02 GMT on 30 October, with 1,766 entries. Neither CVE-2026-116606 nor CVE-2026-111560 is in it. The catalogue is three days older than the records (derived), so it could not yet have reflected them. Absence from KEV on this date says only that CISA had not listed them. When read on 2 November, neither Barracuda's page nor Mandiant's file said anything about exploitation in the wild (Barracuda's page now does: see the update at the top), and the NVD entry is still Awaiting Analysis, so it carries no CISA assessment.
The same catalogue does hold one earlier ESG entry, CVE-2023-2868, added 2023-05-26 and described there as an improper input validation vulnerability of a user supplied .tar file leading to remote command injection. The two sources about this flaw do not mention it. It is not evidence about CVE-2026-116606, and the only reason to note it is that readers will look for it. A history of past ESG flaws is context for how much attention an appliance deserves. It is not proof of anything here.
No source gives a number of exposed appliances. Barracuda's own wording, that organisations whose interfaces are not publicly accessible are less exposed, is the only exposure statement.
What to do, in order
Take this with you
Ranked checklist, grounded in the sources read
- Confirm the ESG firmware version on every appliance. Move to 9.4.0.030 or later, which is the CVE record's boundary, and apply the Barracuda patches BNSF-40425 or BNSF-40430 as Barracuda's table directs. Barracuda says the device shows the latest firmware version available, and that several updates may be needed.
- Check that automatic patching is on. Barracuda says that if it is turned off, it recommends setting devices to receive patches automatically.
- Restrict the administrative interface to trusted internal networks. This is Barracuda's own advice. Until the vendor and the CVE record agree on whether authentication is needed, plan around the harsher reading: this site's suggestion is to assume that network reach to the interface is enough.
- Review the appliance configuration and administrator accounts for unexpected changes and compare them with a known good backup. This is this site's suggestion. Barracuda publishes no indicators of compromise.
- Ask Barracuda Support in writing whether the patches correspond to 9.4.0.030, whether administrative authentication is required to reach the import function, and whether it has detection guidance. This is this site's suggestion, because the page leaves all three open.
- CISA added both CVEs to its Known Exploited Vulnerabilities catalogue on 10 November, due 13 November, with forensic triage marked Yes. Keep watching Barracuda's page, read on 2, 7 and 10 November, which can change.
Technical details
Barracuda's page, the CVE records and Mandiant's two files print no request, payload, command, log line, hash, domain or address for this flaw, and none is reproduced here. The artifacts they do print are the description, the scores, the versions, the patch table and the dates. A defender uses the versions to check inventory, the description to understand what to hunt, and the dates to anchor an investigation. Nothing below is exploit code.
The CVE record's description for CVE-2026-116606, which the GitHub advisory and the NVD entry repeat word for word. Copied exactly, including its apostrophe.
An authentication bypass in Barracuda Email Security Gateway versions earlier than 9.4.0.030 allows an unauthenticated remote attacker to invoke a configuration-import function and restore a crafted, compatible backup archive, resulting in unauthorized modification of the appliance’s global configuration.
The CVSS 4.0 vector and score in the CVE record. Privileges Required is NONE here. The same vector is printed in Mandiant's file with the score in brackets.
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
baseScore 9.3 baseSeverity CRITICAL
CWE-288: Authentication Bypass Using an Alternate Path or Channel
CAPEC-115: Authentication Bypass
The affected version range as the CVE record gives it, formatted onto lines by this site (derived layout, values exact). The NVD entry repeats it. Use it to check which ESG firmware strings fall below the boundary.
vendor: Barracuda Networks
product: Barracuda Email Security Gateway (ESG)
status: affected
version: 0
lessThan: 9.4.0.030
versionType: custom
defaultStatus: unaffected
Barracuda's advisory block for the same CVE, and the ESG row of its patch table (the table row is laid out on one line by this site, values exact). Note the two lines that bear on the authentication question.
CVE: CVE-2026-116606
Vulnerability Type: Pre-Authentication Authorization Bypass
Affected Product: ESG
Severity: High
CVSS Score: 9.3
Authentication Required: Yes, administrative access
Remediation: Upgrade to the latest firmware version
Advisory Published: November 2, 2026
Advisory Updated: November 2, 2026
Patch for Email Security Gateway (ESG): BNSF-40425 (9.4.017+), BNSF-40430 (<9.4.017)
Mandiant's disclosure timeline for the configuration import flaw, copied from its advisory file, and its exploitability line, which the CVE record's scoring follows.
* 2026-10-22: Reported by Barracuda
* 2026-11-02: CVE published and Mandiant advisory released
Exploitability
High: The vulnerability is exposed to an unauthenticated remote attacker.
The companion flaw, CVE-2026-111560, whose description names the field involved. This is the vendor's and Mandiant's description of a weakness, with no value, field syntax or payload. Affected ESG range from Mandiant's file.
Improper neutralization of shell metacharacters in the timezone configuration field in certain Barracuda appliance products using common Barracuda code allows an authenticated administrator to inject OS commands that execute with root privileges when the crafted timezone value is subsequently processed.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
baseScore 8.6 baseSeverity HIGH
Barracuda Email Security Gateway (ESG) <= 9.4.0.27
The result of this site's own check of the CISA catalogue, a derived summary of what it contained, not a copy of CISA's text. Re-run it before relying on it.
catalogVersion: 2026.10.30
dateReleased: 2026-10-30T17:02:45Z
entries: 1766
CVE-2026-116606 present: false
CVE-2026-111560 present: false
Barracuda entries in catalogue: CVE-2023-2868 (Email Security Gateway (ESG) Appliance), dateAdded 2023-05-26
The question that exposes the gap
A mail gateway is trusted because it stands between the internet and the inbox. A flaw that lets someone replace its global configuration is serious whichever party is right about the login. But the two readings lead to different priorities, and the vendor and the CNA published them on the same day. If an unauthenticated caller can restore a configuration on an ESG, why does Barracuda's own table say Authentication Required: Yes, and if a login is required, why does the CVE record score Privileges Required as None? Until one of them corrects its page, which one should the owner of an exposed appliance believe?
Key facts
Sources
- PrimaryBarracuda's advisory page 'Pre-Authentication Authorization Bypass and Command Injection Vulnerabilities in Certain Barracuda Products', page data dated 2 November 2026: affected products, patch IDs, guidance, Authentication Required wording, severity and score. Read in fullBarracuda Networksaccessed 2026-11-02
- PrimaryCVE-2026-116606 record: description, CVSS 4.0 vector and 9.3 CRITICAL score, CWE-288, affected versions earlier than 9.4.0.030, reserved 26 October, published 2 November 2026CVE Program (Mandiant as CNA)accessed 2026-11-02
- PrimaryCVE-2026-111560 record: timezone field command injection, authenticated administrator, 8.6, affected ESG up to 9.4.0.27 and five other products, reserved 16 October, published 2 November 2026CVE Program (Mandiant as CNA)accessed 2026-11-02
- PrimaryMandiant advisory file MNDT-2026-0042 for CVE-2026-116606: description, impact, exploitability, the disclosure timeline of 22 October and 2 November 2026. Read in full, about 1.4 KB, no exploit contentMandiantaccessed 2026-11-02
- PrimaryMandiant advisory file MNDT-2026-0041 for CVE-2026-111560: affected products and versions, exploitability, the 15 October report dateMandiantaccessed 2026-11-02
- PrimaryGitHub advisory GHSA-9fcr-mp7p-hprv via the API: unreviewed, severity critical, published 2 November 2026 15:31 GMT, repeats the CVE description and CVSS 4.0 vectorGitHub Advisory Databaseaccessed 2026-11-02
- PrimaryNVD record for CVE-2026-116606: Awaiting Analysis, Mandiant's CVSS 4.0 score shown as secondary, published 2 November 2026 13:17 GMTNIST National Vulnerability Databaseaccessed 2026-11-02
- PrimaryKnown Exploited Vulnerabilities catalogue, versions 2026.10.30 (1,766 entries, neither CVE present) and 2026.11.10 (released 2026-11-10T19:03:29Z, 1,779 entries, both CVEs added 10 November, due 13 November); one earlier Barracuda ESG entry, CVE-2023-2868CISAaccessed 2026-11-02
- PrimaryBarracuda Email Security Gateway Pre-Auth Remote Root RCE, CVE-2026-116606 and CVE-2026-111560, 5 November 2026: patch diff of 9.4.0.027 and 9.4.0.029, chained unauthenticated request to root, detection artefact generatorwatchTowr Labsaccessed 2026-11-07


