Advisory

CVE-2026-111560: Barracuda Networks OS Command Injection (CVSS 8.6 HIGH) — Active Exploitation Confirmed

An OS command injection flaw in multiple Barracuda Networks appliance products allows an authenticated administrator to inject shell commands that execute with root privileges by crafting a malicious timezone configuration value. CISA has added this vulnerability to the Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild.

TL;DR: Apply all available vendor mitigations immediately and follow CISA BOD 26-04 patching guidance; if no mitigation exists for your deployment, consider discontinuing use of the affected product until a fix is available.

What Is the Flaw?

CVE-2026-111560 is an OS command injection vulnerability classified under CWE-78 (Improper Neutralization of Special Elements used in an OS Command). The root cause is insufficient sanitization of shell metacharacters within the timezone configuration field shared across a common Barracuda code base.

When an authenticated administrator saves a crafted timezone value, the appliance later processes that value in a context where it is passed to the underlying operating system without adequate escaping. This allows arbitrary OS commands to be injected and executed with root privileges.

According to the CISA KEV catalog entry, this vulnerability can be chained with CVE-2026-116606, compounding the potential impact. Defenders should treat both CVEs together when assessing exposure.

The vulnerability carries a CVSS 4.0 score of 8.6 (HIGH) with the vector 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, reflecting network-reachable attack delivery, low attack complexity, and high impact to confidentiality, integrity, and availability of the affected system.

Who and What Is Affected?

The vulnerability affects multiple Barracuda Networks appliance product lines that share the vulnerable common Barracuda code. Per the CISA KEV catalog, the confirmed affected products are:

  • Email Security Gateway (ESG)
  • Load Balancer
  • Application Delivery Controller (ADC)
  • Message Archiver (BMA)
  • WAF Control Center (WCC)
  • Web Application Firewall (WAF)
  • Web Security Gateway (WSG)

Specific affected firmware or software versions were not enumerated in the available facts. Consult Barracuda Networks' own advisory for precise version ranges and confirm whether your deployed versions are in scope.

Organizations operating any of these appliances — whether on-premises or in cloud-hosted configurations — should treat them as potentially exposed until vendor guidance has been fully applied and verified.

What Is the Impact?

Successful exploitation grants an attacker root-level command execution on the affected appliance. At that privilege level, an attacker can:

  • Read, modify, or destroy all data processed by the appliance, including email, archived messages, and web traffic logs.
  • Pivot into adjacent network segments that the appliance is positioned to inspect or forward traffic for.
  • Persist on the device by modifying firmware, installing backdoors, or disabling security controls.
  • Chain this vulnerability with CVE-2026-116606 for a broader or more damaging attack scenario, as noted by CISA.

The CVSS 4.0 score of 8.6 HIGH reflects high impact across confidentiality, integrity, and availability of the vulnerable system. While the vector indicates that high privileges are required (PR:H), meaning the attacker must already hold administrator credentials, this prerequisite should not be dismissed: administrator accounts on network appliances are frequently targeted via credential stuffing, phishing, or lateral movement from other compromised systems.

CISA has confirmed this vulnerability is actively exploited and added it to the KEV catalog on 2026-11-10. Active exploitation means that theoretical risk has become operational threat.

What Should You Do Right Now?

CISA's required action for this KEV entry is clear: apply mitigations in accordance with vendor instructions and ensure compliance with CISA BOD 26-04 (Prioritizing Security Updates Based on Risk). The specific steps organizations should take, in priority order:

  1. Identify all affected assets immediately. Inventory every Barracuda ESG, Load Balancer, ADC, BMA, WCC, WAF, and WSG appliance in your environment, noting whether each is internet-facing.
  2. Apply vendor-supplied patches or mitigations. Consult the official Barracuda Networks security advisory for available patches. If Barracuda has issued replacement firmware, apply it promptly. Do not wait for a maintenance window for a KEV-listed vulnerability.
  3. Discontinue use if no mitigation is available. CISA explicitly states that if mitigations are unavailable, organizations should consider discontinuing use of the product. This is especially relevant for internet-exposed deployments.
  4. Restrict administrative access. While applying patches, reduce the attack surface by restricting management interface access to known, trusted IP ranges. Multi-factor authentication on administrator accounts should be enforced wherever possible.
  5. Treat this alongside CVE-2026-116606. Since CISA notes these can be chained, remediate both vulnerabilities concurrently and verify neither is present in your environment.
  6. Conduct forensic triage. CISA's KEV guidance for this entry includes specific forensic triage requirements. If you have reason to believe your appliance may have been targeted, follow CISA's forensics guidance (referenced in the KEV catalog notes) before returning appliances to production.
  7. Monitor for indicators of compromise. Review appliance logs for anomalous activity, unexpected outbound connections, or configuration changes — particularly around timezone settings — both before and after patching.

Primary references: CISA KEV Catalog, NVD entry for CVE-2026-111560, and the Barracuda Networks official security advisory.

How Continuous External Testing Surfaces This Exposure

Appliances like Barracuda's ESG, WAF, and ADC are by design positioned at the perimeter — often directly internet-facing or handling internet-bound traffic. This makes them ideal candidates for continuous external attack surface monitoring.

A continuous external testing programme can help your organisation in the following ways when a vulnerability like CVE-2026-111560 is disclosed:

  • Fingerprinting internet-exposed appliances. External scanning can identify which Barracuda appliance products and versions are reachable from the public internet, giving your team an accurate inventory without relying solely on internal records.
  • Detecting newly exposed management interfaces. Administrative interfaces that have inadvertently become internet-accessible — increasing the viability of exploitation — are surfaced before an attacker finds them.
  • Validating patch application from the outside. After applying vendor mitigations, external testing confirms that the patched version is what is actually being served to the internet, catching misconfigurations where the wrong firmware is running on a specific node.
  • Tracking the chained CVE surface. When CISA flags a chaining relationship (as with CVE-2026-116606 here), external testing can assess whether both components of the chain are exposed simultaneously.
  • Providing near-real-time alerting. Because KEV-listed vulnerabilities are actively exploited, the window between patch availability and exploitation is compressed. Continuous — not periodic — testing is what delivers the speed needed to respond within that window.

Internal vulnerability scanners and agent-based tools provide important complementary data, but they cannot replicate the perspective of an attacker probing from the internet. For perimeter appliances specifically, the external view is the most operationally relevant one.

Sources & further reading: NVD CVE-2026-111560 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: github.com, trust.barracuda.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Does an attacker need administrator credentials to exploit CVE-2026-111560?

Yes. The CVSS 4.0 vector includes PR:H (Privileges Required: High), meaning an attacker must already hold authenticated administrator-level access to the affected appliance management interface before the injection can be triggered. However, CISA has confirmed active exploitation, so the prerequisite has not prevented real-world attacks. Restricting and hardening administrator access is an important compensating control while patches are applied.

Which Barracuda products are confirmed as affected?

Per the CISA KEV catalog entry, the confirmed affected products are: Email Security Gateway (ESG), Load Balancer, Application Delivery Controller (ADC), Message Archiver (BMA), WAF Control Center (WCC), Web Application Firewall (WAF), and Web Security Gateway (WSG). Specific version ranges were not enumerated in the available facts; consult Barracuda Networks' own security advisory for precise version information.

What does it mean that this vulnerability can be 'chained' with CVE-2026-116606?

CISA's KEV entry states that CVE-2026-111560 can be chained with CVE-2026-116606. Chaining means the two vulnerabilities can be combined in a single attack sequence, potentially allowing an attacker to achieve an outcome that neither vulnerability enables on its own — for example, escalating from a lower-privilege position or crossing a boundary that one flaw alone would not breach. Organizations should evaluate and remediate both CVEs together rather than in isolation.

Is there a workaround if a patch is not yet available for my deployment?

CISA's required action states that if mitigations are unavailable, organizations should follow applicable BOD 26-04 guidance for cloud services or consider discontinuing use of the product. As an interim compensating control, restricting access to the administrative management interface to trusted IP ranges only reduces the pool of potential attackers who could reach the vulnerable configuration field, but it does not eliminate the vulnerability itself.