ZeroDayAlert

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

Barracuda Networks 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) contain an OS command injection vulnerability. This vulnerability could allow an authenticated administrator to inject OS commands that execute with root privileges when the crafted timezone value is subsequently processed. This vulnerability can be chained with CVE-2026-116606

Barracuda Networks Multiple Products Added to KEV 2026-11-10 Federal due 2026-11-13 Known ransomware use

Required action — quoted from CISA

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.

Where this comes from. The identifier, product, dates and required action above are copied verbatim from the CISA Known Exploited Vulnerabilities catalog. The action plan below is written by an AI agent from that record and published automatically. AssurePort has not independently tested this vulnerability and makes no claim about whether any specific system is affected.

Who is affected

This vulnerability affects multiple Barracuda Networks products: 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). The record does not specify which versions are vulnerable, and does not identify whether cloud-hosted variants are affected separately from on-premises deployments.

How to check whether this touches you

  • Inventory your security appliances and check whether any are Barracuda products from the list above (ESG, Load Balancer, ADC, BMA, WCC, WAF, WSG).
  • Determine whether each appliance is reachable by authenticated administrators from your network or from the internet; command injection requires authentication, so external exposure is relevant only if you permit remote administrative access.
  • Retrieve the running firmware version from the administrative interface or system logs; version strings alone do not confirm whether a backport has been applied, so check the vendor's security advisory for the specific build numbers or dates that contain the fix.

What to do

  1. Obtain Barracuda's security advisory and patch schedule; confirm whether a fix is available for your product variant and version.
  2. If no patch is available yet, restrict administrative access to your appliance by IP address allowlist or by disabling remote login; this reduces the attack surface to administrators on your network.
  3. Review and retain administrative audit logs covering timezone configuration changes; OS command injection via timezone values would typically be visible in configuration change logs.
  4. If you cannot apply mitigations within your risk tolerance, follow CISA BOD 26-04 guidance for cloud services or plan for discontinuation of the product if the vendor offers no remediation path.
  5. If the product is internet-facing and hosts critical security functions (such as email filtering), escalate the patch requirement to your change advisory board with a target date aligned with federal remediation guidance.

If you find you were exposed

Exploitation of an authenticated command injection vulnerability typically leaves evidence in administrative logs, system command execution logs, and audit trails of configuration changes. Search your appliance logs for any timezone configuration modifications or unexpected administrative logins dating back several months before the vulnerability disclosure, since exploitation often precedes public notice. Log retention on security appliances is frequently limited to weeks or months; if you lack logs covering the period before disclosure, document the gap and establish a longer retention policy for future incidents.

Get these the morning they land.

One email, only when a vulnerability is newly confirmed as exploited — the CISA record plus our action plan. No more than one a day, and nothing on quiet days.

Knowing it exists is not the same as knowing you are exposed.

This page can tell you that CVE-2026-111560 is being exploited. It cannot tell you whether Multiple Products is running somewhere of yours that is reachable. That question is what a scan answers.

Check your own surface →