Skip to content
Blog

Barracuda · Barracuda Email Security Gateway · ESG

Barracuda ESG: CVE-2026-116606 and CVE-2026-111560 Added to KEV, a Pre-Auth Chain to Root

CISA adds two chainable Barracuda CVEs to KEV: an unauthenticated config import on ESG, then root command injection. Federal deadline is November 13.

4 min readCVE-2026-116606CVE-2026-111560

On November 10, 2026, CISA added two Barracuda vulnerabilities to its Known Exploited Vulnerabilities catalog. Both were published in NVD on November 2: CVE-2026-116606, an authentication bypass in the Email Security Gateway (ESG), and CVE-2026-111560, an OS command injection shared by several Barracuda appliances. CISA notes in both entries that they can be chained: the first gets an attacker in without credentials, the second turns admin access into command execution as root.

The remediation deadline for US federal agencies says a lot: November 13, 2026, three days after the listing instead of the usual two weeks.

CVE-2026-116606CVE-2026-111560
ProductBarracuda Email Security GatewayESG, Load Balancer, ADC, Message Archiver, WAF, WAF Control Center, Web Security Gateway
WeaknessAuthentication bypass via alternate path (CWE-288)OS command injection (CWE-78)
PrerequisiteNone (unauthenticated, remote)Administrator account
CVSS 4.0 (Mandiant)9.3 CRITICAL8.6 HIGH
NVD statusUndergoing AnalysisUndergoing Analysis
Added to KEV2026-11-102026-11-10
CISA due date2026-11-132026-11-13

The scores come from Mandiant (Google), which reported both flaws. NVD has not yet published its own assessment or any CPE configuration. CISA lists ransomware use as "Unknown".


How the chain works

CVE-2026-116606: per NVD, an unauthenticated remote attacker can call the ESG's configuration-import function and restore a crafted, compatible backup archive. The result is an unauthorized change to the appliance's global configuration. Mandiant's vector requires no privileges and no user interaction (PR:N, UI:N), with high confidentiality, integrity and availability impact.

CVE-2026-111560: the timezone configuration field does not neutralize shell metacharacters. An authenticated administrator can embed commands there, and they run with root privileges when the value is processed later. On its own it requires an admin account (PR:H), hence the lower score.

The combination is what matters. Restoring a configuration of the attacker's choosing effectively means deciding what the appliance's configuration contains, and the timezone is part of it. The public data does not spell out the exact exploitation path; this is our reading of CISA's "chainable" note, not a published write-up.

An email gateway sees every message entering and leaving the organization. Root on that box potentially exposes mail, relays and whatever credentials are configured on it.


Affected versions

  • CVE-2026-116606: the NVD description covers ESG earlier than 9.4.0.030. That is the only version bound published.
  • CVE-2026-111560: NVD refers to "certain Barracuda appliance products using common Barracuda code" without versions. The product list (ESG, Load Balancer, ADC, Message Archiver, WAF, WAF Control Center, Web Security Gateway) comes from the KEV entry.

NVD has no CPE configuration yet. For the version to install on each product, the reference is Barracuda's advisory (trust.barracuda.com, "pre-authentication-authorization-bypass-command-injection"), along with Mandiant's MNDT-2026-0041 and MNDT-2026-0042 disclosures.


Detection

  • Inventory: list every Barracuda appliance you run, not just ESG. CVE-2026-111560 spans several product families.
  • ESG version: check the admin interface for anything below 9.4.0.030.
  • Admin logs: look for configuration imports or restores nobody initiated, and for any timezone change.
  • Current configuration: diff it against a known-good backup (relays, accounts, mail routing rules).
  • Exposure: make sure the admin interface is not reachable from the internet.

CISA ties these listings to its forensic triage requirements (BOD 26-04): an appliance that was exposed should be investigated as potentially compromised, not just patched.


Mitigation

  1. Apply Barracuda's fixes per the vendor advisory, internet-facing ESG first.
  2. Restrict the admin interface to a management network.
  3. Hunt for compromise before calling the appliance clean: a patch does not undo a configuration that was already altered.
  4. Rotate secrets stored on the appliance (accounts, relay keys, directory connectors) if there is any doubt.
  5. Do not wait for NVD's analysis: the status still reads "Undergoing Analysis", but CISA has confirmed exploitation.

Why continuous monitoring of your security gateways matters

Email and web filtering appliances are internet-facing by design, and they keep landing in the KEV catalog with very short deadlines. Knowing which ones you run, and on which version, is what lets you act the same day.

With cveo.tech, add your Barracuda appliances to your inventory and get an alert as soon as a new CVE or KEV listing affects them.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.