CVE-2026-111560 - Barracuda Networks Multiple Products OS Command Injection Vulnerability

CVE-2026-111560

Barracuda Appliances - Root Command Injection via the Timezone Configuration Field

What is the Barracuda appliance family?

Barracuda Networks sells a family of network security appliances that share a common codebase and a common web administration interface. Six of them are affected here: the Email Security Gateway (ESG), which filters inbound and outbound mail; the Load Balancer Application Delivery Controller (ADC), which fronts application servers; the Web Application Firewall (WAF) and its fleet manager, the WAF Control Center (WCC); the Web Security Gateway (WSG), a web filtering proxy; and the Message Archiver (BMA), which retains mail for compliance and e-discovery.

Each of these devices sits inline on a traffic path and holds credentials, keys, or message content for the organization behind it. An attacker with root on one of them is not merely on a server, but inside the inspection point for the traffic it guards. The shared codebase is what makes this CVE a six-product problem rather than a one-product problem: a single unsanitized configuration field in common code reappears in every appliance that uses it.

Overview

CVE-2026-111560 is an OS command injection in the timezone configuration setting. The value an administrator sets for the appliance timezone is passed into a shell command without neutralizing shell metacharacters. A helper script invoked through sudo then runs that command, so injected content executes as root when the crafted timezone value is processed.

On its own this is a privilege escalation for someone who already holds an administrator account: it converts administrative access to the web interface into root on the underlying operating system, which is not supposed to be available to any customer-facing role. Mandiant scores it 8.6 High under 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), with the PR:H metric reflecting that administrator requirement. NVD has since published its own score of 7.2 High under CVSS 3.1 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), which is the rating shown in the severity badge above. The two agree on severity band and differ only in how each version weighs a high-privilege precondition.

On the ESG specifically, the administrator requirement disappears. CVE-2026-116606, a pre-authentication authorization bypass in the same interface, lets an unauthenticated attacker restore a crafted configuration backup, and a backup can set the timezone. Chained, the two take an attacker from no credentials to root on the appliance. Barracuda confirmed exploitation activity on 2026-11-09 and CISA added both CVEs to the KEV catalog on 2026-11-10 with a three-day deadline of 2026-11-13.

Affected Versions

Product Vulnerable Fixed
Email Security Gateway (ESG) 9.4.0.27 and earlier Patch BNSF-40425 (9.4.017+) or BNSF-40430 (earlier builds); firmware 9.4.0.030 recommended
Load Balancer ADC 6.4.0 and earlier Patch BNADC-16586
Web Application Firewall (WAF) 11.0.1 and earlier Patch BNADC-16586
WAF Control Center (WCC) 2.2.1 and earlier Patch BNWF-60060
Web Security Gateway (WSG) 16.1.100.100 and earlier Patch BNYF-24789
Message Archiver (BMA) 5.5.4.0 and earlier Patch BNMA-32468

Version ranges come from Mandiant's advisory; Barracuda's own advisory names the patch identifiers rather than version boundaries, so verify both the firmware level and the applied patch.

Technical Details

The weakness is CWE-78, improper neutralization of special elements used in an OS command. In plain words: a configuration value that a human types into a form is dropped straight into a shell command line, so characters that mean something to the shell, a semicolon, a backtick, a $(...) substitution, are executed as commands rather than treated as part of a timezone name. The field in question is the system timezone, reported in public analysis as system_timezone.

The escalation to root comes from how the value is consumed. The timezone is not applied by the web process directly but by a helper script invoked through sudo, which runs with root privileges. Anything injected into the value therefore inherits root rather than the web application's own account. Execution is deferred: it happens when the crafted timezone value is next processed, not necessarily at the moment it is written.

Taken alone the attack needs network access to the administration interface plus administrator credentials, with low complexity and no user interaction. Taken as the second half of the ESG chain it needs neither credentials nor user interaction, because the configuration backup restore reached through CVE-2026-116606 supplies the timezone value. watchTowr Labs demonstrated the full path by writing a file to an ESG appliance as root.

Discovery

Mandiant is the CVE Numbering Authority and published advisory MNDT-2026-0041 on 2026-11-02. Its disclosure timeline records the command injection as reported to Barracuda on 2026-10-15, a week before the companion authentication bypass. Mandiant credits the report to Barracuda and does not name an individual researcher, and Barracuda's advisory names none either.

The public technical description of the injection, including the shared helper script and the sudo path to root, came from watchTowr Labs, which reverse-engineered the 2026-11-02 patch and published its analysis along with a detection artifact generator. Reports place that release between 2026-11-03 and 2026-11-05.

Exploitation Context

Barracuda updated its Trust Center advisory on 2026-11-09 to state that it had identified exploitation activity affecting a small number of organizations. It has not disclosed whether attackers used this CVE alone or as part of the ESG chain, has named no threat actor, and has published no indicators of compromise. CISA's entry does not flag known ransomware use.

The realistic risk splits by product. On ESG, this is the payload half of an unauthenticated remote root chain and should be treated as critical regardless of the 8.6 score. On ADC, WAF, WCC, WSG, and BMA, no companion bypass has been published, so exploitation still requires administrator access: the threat there is an insider, a reused or stolen administrator credential, or a session hijacked through some other flaw, with this CVE converting that foothold into root on the appliance.

No exposure counts from Shadowserver, Censys, or GreyNoise had been published as of 2026-11-10. Barracuda notes that appliances whose administration interfaces are not reachable from the internet are substantially less exposed, which is the main variable separating a theoretical risk from an urgent one.

Remediation

  1. Apply the product-specific security patch from the table above to every affected appliance: BNSF-40425 or BNSF-40430 for ESG, BNADC-16586 for ADC and WAF, BNWF-60060 for WCC, BNYF-24789 for WSG, BNMA-32468 for BMA. Do not assume a recent firmware number means the patch is present; check both.
  2. On ESG, upgrade firmware to 9.4.0.030 or later. That single upgrade covers this CVE and CVE-2026-116606, which is the one that makes this exploitable without a login.
  3. Re-enable automatic security patching wherever it was disabled. Barracuda highlights this because appliances with it turned off did not receive the 2026-11-02 fix.
  4. Restrict every appliance administration interface to a management network or VPN. This is the only effective control for an unpatched device and it also removes the practical path to the ESG chain.
  5. Treat an unpatched, internet-exposed ESG as potentially compromised. Because the outcome is root, patching does not remove an attacker who already has a foothold. Compare the running configuration against a known-good backup, inspect the timezone setting for shell metacharacters, and look for unexpected accounts, SSH keys, cron entries, and startup script modifications.
  6. Review administration interface and system logs for timezone changes nobody made, for configuration import or restore events, and for administrative logins from unfamiliar addresses. Look back to at least 2026-11-02 and preferably to 2026-10-15. Preserve logs and appliance state before remediating, in line with CISA's Forensics Triage Requirements under BOD 26-04.
  7. Federal civilian agencies must remediate or discontinue use by 2026-11-13. The short window reflects confirmed exploitation and published analysis; other operators should treat it as the outer limit.

Key Details

PropertyValue
CVE ID CVE-2026-111560
Vendor / Product Barracuda Networks - Multiple Products
NVD Published2026-11-02
NVD Last Modified2026-11-12
CVSS 3.1 Score7.2
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
SeverityHIGH
CWE CWE-78 find similar ↗
CISA KEV Added2026-11-10
CISA KEV Deadline2026-11-13
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

CISA BOD 26-04 Deadline: 2026-11-13. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA's "Forensics Triage Requirements" (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Timeline

DateEvent
2026-10-15Barracuda receives the command injection report (per Mandiant's disclosure timeline)
2026-11-02Barracuda publishes its Trust Center advisory and ships patches for all six products; CVE published alongside Mandiant advisory MNDT-2026-0041
2026-11-05watchTowr Labs publishes the chain analysis, demonstrating root file write on an ESG appliance
2026-11-09Barracuda updates the advisory to confirm exploitation activity affecting a small number of organizations
2026-11-10Added to CISA Known Exploited Vulnerabilities catalog
2026-11-12NVD publishes a CVSS 3.1 base score of 7.2 (High)
2026-11-13CISA BOD 26-04 remediation deadline