~/f4n6 $ grep -r "Barracuda ESG auth bypass CVE-2026-116606 added to CISA KEV" ./investigations/ --include="*.md"

Barracuda ESG auth bypass CVE-2026-116606 added to CISA KEV

Jeff Davies 10 Nov 2026 7 min read

1. Executive summary

CVE-2026-116606, a pre-authentication authorization bypass in Barracuda Email Security Gateway (ESG), was added to CISA KEV on 2026-11-10 with a CVSS score of 9.3 (critical) and an EPSS of 2%. Barracuda states it has identified exploitation activity affecting a small number of organizations, and the flaw chains with CVE-2026-111560 (CVSS 8.6, high, also in CISA KEV since 2026-11-10) to give an attacker root on the appliance. The exposure is limited to ESGs whose administrative interface is reachable by an attacker, so internet-facing admin UIs carry the immediate risk. For EMEA financial services the concern is an email gateway that sits in the mail path and holds configuration and message data; a compromised appliance is a foothold on the perimeter rather than an isolated email problem. No actor has been attributed in public reporting.

2. Regulatory framing

Article Trigger (the fact in this item) Practical impact
DORA Art. 17 Barracuda reports exploitation activity affecting a small number of organizations, and the chained flaws give root on an ESG that sits in the mail path The ICT-related incident management process must cover detection, containment and recovery for a compromised email gateway, not only mailbox-level incidents
DORA Art. 19 Active exploitation of a KEV-listed flaw in a product an institution may run as an ICT third-party service If the incident is classified as major, reporting to the competent authority follows the Art. 18 classification; the KEV listing and vendor exploitation statement are inputs to that classification
NIS2 Art. 21(2)(d) The vulnerability is in a third-party email security product, and exploitation is confirmed by the vendor Supply chain security measures must include tracking vendor advisories and exploitation status for perimeter email components

3. Technical analysis & attack chain

The two CVEs are designed to be used together. CVE-2026-116606 is an authentication bypass using an alternate path or channel (CWE-288) that lets an unauthenticated remote attacker invoke a configuration-import function and restore a crafted, compatible backup archive, which modifies the appliance's global configuration. CVE-2026-111560 is an OS command injection (CWE-78) in which an authenticated administrator can inject OS commands that execute with root privileges when a crafted timezone value is subsequently processed. Barracuda's own wording is that, exploited in combination, the flaws "could allow an attacker to bypass authorization controls and obtain root access to the device."

Confirmed steps in the chain, as described in the sources:

  1. The attacker reaches the ESG administrative user interface. Authentication is not required to exploit CVE-2026-116606, but the attacker must have access to the admin UI, so network reachability of that interface is the precondition.
  2. The attacker uses CVE-2026-116606 to invoke the configuration-import function and restores a crafted, compatible backup archive. This modifies the appliance's global configuration without a valid login.
  3. The configuration change sets up the condition for CVE-2026-111560: a crafted timezone value that is processed later and results in OS command execution with root privileges.

The mechanism that matters to a defender is the configuration-import path. An unauthenticated restore of a backup archive is a configuration-write primitive, and the second flaw turns a configuration value (the timezone) into root command execution. Barracuda rates CVE-2026-116606 at 9.3 and CVE-2026-111560 at 8.6; both are in CISA KEV as of 2026-11-10, and CISA's required action cites a due date of 2026-11-13.

Affected products differ between the two CVEs. CVE-2026-116606 is recorded against Barracuda Email Security Gateway (ESG). CVE-2026-111560 affects multiple Barracuda products: ESG, Load Balancer, Application Delivery Controller (ADC), Message Archiver (BMA), WAF Control Center (WCC), Web Application Firewall (WAF), and Web Security Gateway (WSG). An estate that runs any of these should treat the command-injection half as in scope even where ESG is not deployed.

Barracuda released patches, and The Register reports the vendor disclosed and fixed the vulnerabilities the week before 2026-11-10. The sources do not give the specific fixed version numbers, the exact archive format accepted by the import function, or the file paths and commands involved; those are not stated in public reporting and should be taken from the Barracuda advisory.

What the sources do not establish: who is responsible, how many organizations were affected beyond "a small number," whether the intruders obtained root in the observed activity, and what data, if any, was taken. The Register notes that if root was obtained an attacker could steal data, install backdoors and take full control, which is a statement of capability, not of what happened here. The 2023 FBI attribution of ESG attacks to PRC-linked actors is background about a prior campaign, not an attribution for this event.

Single-source caveat: the "small number of organizations" exploitation statement and the patch timing rest on Barracuda's advisory as reported by The Register. The technical chain detail rests on Barracuda's advisory and watchTowr's write-up as reported by The Hacker News. Verify against the vendor advisory before relying on either for incident scoping.

4. Mitigation & containment

P1 (within 24 hours)

  • Remove internet reachability of the ESG administrative UI. Tausif Ahmed of Purplecop Security, quoted by The Register, put it directly: "If your Email Security Gateway's admin UI is open to the internet, that's the first thing I'd close today." Restrict the admin interface to a management network or named source addresses at the firewall.
  • Apply the Barracuda patches for CVE-2026-116606 and CVE-2026-111560. CISA's required action is to apply mitigations per vendor instructions, with a due date of 2026-11-13. The sources do not name the fixed version numbers; take them from the Barracuda advisory.
  • Hunt for unauthorised configuration imports on ESG appliances: review configuration-change and admin-UI access logs for import or restore events that do not correspond to a change ticket, and for admin-UI sessions from unexpected source addresses.
  • On any ESG, ADC, BMA, WAF, WCC or WSG in the estate, treat CVE-2026-111560 as in scope and confirm the patch state, since the command-injection half affects all of these products.

P2 (within 72 hours)

  • Where an appliance shows signs of an unauthorised configuration import, treat it as potentially root-compromised: isolate it from the network, preserve logs and configuration for forensics, and rebuild from a known-good image rather than cleaning in place. CISA's required action references its "Forensics Triage Requirements."
  • Review timezone and other global configuration values on ESG appliances for unexpected changes, since the command-injection half is triggered when a crafted timezone value is processed.
  • Confirm that no backup archive of unknown provenance has been restored to an appliance, and restrict who can perform configuration imports.

P3 (within 7 days)

  • Add the ESG admin UI and the other affected Barracuda products to external attack-surface review so that management interfaces are not re-exposed.
  • Fold the KEV status of both CVEs into the patch-prioritisation process, and record the vendor exploitation statement as an input to incident classification.

5. Indicators of compromise

No indicators of compromise available in the source material.

The sources describe the mechanism (an unauthenticated configuration import of a crafted backup archive, and a crafted timezone value leading to root command execution) but give no file hashes, network indicators, file paths, registry keys or command strings. The behavioural signals below are derived from the described mechanism and should be validated against the vendor advisory.

Behavioural indicators

behaviour where to observe confidence
Configuration import or restore invoked without a preceding authenticated admin login ESG admin-UI and configuration-change logs Medium; derived from the CVE-2026-116606 mechanism, not from a published IOC
Global configuration modified outside a change window, particularly timezone values ESG configuration audit logs Medium; derived from the CVE-2026-111560 trigger
Admin-UI access from source addresses outside the management network Firewall, reverse proxy and ESG access logs Medium; reachability of the admin UI is the stated precondition

6. Detection

Insufficient indicators to author detection rules.

The sources give no distinctive strings, command-line flags, file names, paths, registry keys or hard-coded values that appear in the malicious artefact. The CVE identifiers and product names are not threat artefacts, and the mechanism descriptions do not supply strings that could be used in a rule without inventing them. Detection should rely on the behavioural indicators in §5 and on the vendor advisory's guidance until atomic indicators are published.

CVE assessment

2 referenced CVEs — 2 actively exploited (CISA KEV), 1 critical (CVSS ≥ 9.0)

CVE CVSS Exploited EPSS Summary
CVE-2026-116606 9.3 Critical ⚠ KEV 2026-11-10 2% An authentication bypass in Barracuda Email Security Gateway versions earlier than 9.4.0.030 allows an unauthenticated remote a…
CVE-2026-111560 8.6 High ⚠ KEV 2026-11-10 1% Improper neutralization of shell metacharacters in the timezone configuration field in certain Barracuda appliance products usi…

7. Sources

  • NVD, CVE-2026-116606, https://nvd.nist.gov/vuln/detail/CVE-2026-116606
  • NVD, CVE-2026-111560, https://nvd.nist.gov/vuln/detail/CVE-2026-111560
  • The Register, "Barracuda's email security gateways bitten by make-me-root vulns," https://www.theregister.com/security/2026/11/10/barracudas-email-security-gateways-bitten-by-make-me-root-vulns/5308883, 2026-11-10
  • The Hacker News, "Experts Demonstrate Barracuda Email Security Gateway Chain Enabling Root Access Without Login," https://thehackernews.com/2026/11/experts-demonstrate-barracuda-email.html
  • SecurityWeek, "Barracuda ESG Authentication Bypass Flaw Opens Path to Root," https://www.securityweek.com/barracuda-email-security-gateway-authentication-bypass-opens-path-to-root/

8. Adverse Trace position

Adverse Trace assesses CVE-2026-116606 as critical (CVSS 9.3, CISA KEV, EPSS 2%) and CVE-2026-111560 as high (CVSS 8.6, CISA KEV, EPSS 1%), with the pair chaining to root on an internet-reachable ESG admin UI. The client impact is concentrated on institutions that expose the ESG management interface or run the other affected Barracuda products, and the vendor's confirmed exploitation activity means this is not a theoretical exposure. No actor is attributed in public reporting, so we make no attribution. The exploitation statement and patch timing are single-sourced to Barracuda as reported by The Register and should be verified against the vendor advisory. We will track the Barracuda advisory for fixed version numbers and any published indicators, and will update this note if either becomes available. Clients should close admin-UI exposure and confirm patch state on every affected product before the 2026-11-13 CISA due date.


Read the original source →

Published via PulseTrace — Adverse Trace threat intelligence.

Post this to LinkedIn
Formatting is converted automatically — headings, bullets, a link back & hashtags. Paste straight in.
J
Jeff Davies