Skip to content
eastbaycyber

CVE-2026-111560: Barracuda OS Command Injection

CVSS · High
7.2
In CISA KEV
Yes
Published
Nov 16
Patch SLA & TriageVector: Local
Immediate (BOD 22-01 due 2026-11-13)

Active exploitation confirmed in CISA KEV.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 7.2
Decode Vector & Sub-Scores →
CVE explainers 11 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-16
⚠
CISA Known Exploited Vulnerability

Active exploitation confirmed in the wild. CISA added this to the KEV catalog on 2026-11-10. Federal agencies must patch by 2026-11-13.

Everything CISA added on 2026-11-10

▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-111560 allows authenticated administrators to inject OS commands that execute as root on affected Barracuda appliances. - ESG, ADC, WAF, WSG, BMA, and WCC versions below the listed fixed releases are affected. - CISA confirms exploitation by listing the CVE in KEV. Patch immediately and investigate exposed systems.

Summary

CVE-2026-111560 is a high-severity Barracuda OS command injection vulnerability in shared appliance code. A maliciously crafted timezone configuration value can contain shell metacharacters. When the appliance later processes that value, injected commands execute with root privileges.

The vulnerability affects multiple Barracuda product families. NVD published it on November 2, 2026, and CISA added it to the Known Exploited Vulnerabilities catalog on November 10, 2026. CISA’s federal remediation deadline was November 13, 2026. That deadline has passed, so affected organizations should treat any unpatched instance as an overdue, high-priority remediation item.

For background on related security advisories, see our vulnerability digest. Organizations reviewing long-term appliance and security telemetry should also understand what log retention means.

Field Value
CVE CVE-2026-111560
Vendor Barracuda Networks
Vulnerability OS command injection through timezone configuration processing
NVD CVSS base score 7.2
Alternate vendor-reported score 8.6 has been reported in secondary material quoting the vendor advisory; do not conflate it with the NVD score
Attack vector Not safely inferable from the retrieved NVD record; the vulnerable management functionality requires administrative access
Authentication / authorization An authenticated administrator is required according to the technical description
Privileges required Administrative privileges
User interaction Not established in the available primary-source material
Patch available Yes
CISA KEV status Yes, added November 10, 2026
Exploitation status Confirmed in the wild by CISA KEV inclusion

The retrieved NVD record did not expose the complete CVSS vector string. This article does not infer individual CVSS components that are not documented in the available research. Defenders should use the NVD record and Barracuda advisory for any scoring-sensitive workflow.

AnalystImpact · assess the risk

Root Cause

The root cause is improper neutralization of shell metacharacters in a timezone configuration field. The appliance accepts a timezone value and later processes it in a context where shell interpretation occurs. If an attacker with administrative access inserts shell syntax into that value, the resulting command is executed by the operating system.

The impact is amplified by the execution context. Injected commands run with root privileges, giving an attacker the ability to alter appliance configuration, access locally stored data, create persistence, modify services, or use the appliance as a foothold for further activity. The precise post-exploitation impact depends on the product, firmware branch, enabled services, and the attacker’s ability to reach the management interface.

The issue appears to affect common Barracuda code shared across several product families. That is why the affected-version list spans email security, application delivery, web security, archiving, and control-center products. Administrators should not assume that a device is safe merely because it is not an ESG appliance; all six product families in the vendor’s affected list require review.

Analyst’s Take: The immediate priority is inventory, not exploit reproduction. CISA has confirmed exploitation, while the available research does not provide a reliable universal payload or complete public exploit. Treat reachable, unpatched appliances as exposure requiring remediation and compromise review.

Who’s Exposed

The following product families are affected when running versions below the specified fixed release:

Product Affected versions Fixed version Additional patch information
Email Security Gateway (ESG) Before 9.4.0.030 9.4.0.030 or later BNSF-40425 for firmware 9.4.017 and later; BNSF-40430 for earlier firmware, as applicable
Load Balancer Application Delivery Controller (ADC) Before 6.4.0 6.4.0 Apply BNADC-16586 as applicable
Web Application Firewall (WAF) Before 11.0.1 11.0.1 Apply BNADC-16586 as applicable
Web Security Gateway (WSG) Before 16.1.100.100 16.1.100.100 Apply BNYF-24789
Message Archiver (BMA) Before 5.5.4.0 5.5.4.0 Apply BNMA-32468
WAF Control Center (WCC) Before 2.2.1 2.2.1 Apply BNWF-60060

Compare versions against the appliance’s actual firmware branch. Product names alone are not sufficient to determine patch applicability. ESG remediation can vary by firmware branch, with different Barracuda patch identifiers reported for firmware 9.4.017 and later versus earlier firmware.

Internet exposure should increase the priority of response, but lack of direct public exposure does not eliminate risk. An attacker who compromises an administrative account, reaches an internal management network, or abuses a trusted remote-access path may still be able to trigger the vulnerable functionality. Inventory standalone appliances, clustered deployments, virtual appliances, management consoles, and devices administered through service-provider or third-party networks.

Technical Notes

The vulnerable input is the timezone configuration field. The available research does not provide a reliable universal payload or a complete public exploit that defenders should copy into production testing. Avoid testing with shell metacharacters on live systems unless Barracuda or an authorized incident-response provider has defined a safe procedure.

Useful inventory fields include:

  • Product family and hostname
  • Firmware version and branch
  • Management interface addresses
  • Internet exposure and upstream access controls
  • Administrative identity providers and privileged accounts
  • Last configuration-change timestamp
  • Barracuda patch identifier and installation status

Severity Breakdown

NVD assigns CVE-2026-111560 a CVSS base score of 7.2. That places the issue in the high-severity category and reflects the consequences of root-level command execution on security appliances. A separate score of 8.6 has been reported in secondary material quoting the Barracuda advisory. Because the available NVD retrieval did not expose the vector string, defenders should preserve both values with their source attribution rather than silently choosing one.

The vulnerability requires administrative authentication, which limits the initial attacker population compared with an unauthenticated remote-code-execution flaw. Appliance administrator accounts are high-value targets, and compromise of an administrative session can convert this prerequisite into root-level operating-system access. Exposed management interfaces and weak segmentation can make exploitation materially easier.

CVSS-related factor Assessment
Confidentiality impact Potentially high because root access may expose appliance data and credentials
Integrity impact Potentially high because root access can alter configuration, services, and stored content
Availability impact Potentially high because commands may disrupt or disable the appliance
Authentication Administrator authentication is required according to the technical description
Exact vector string Not available in the retrieved NVD record; do not infer it
Operational severity High, elevated by confirmed exploitation and appliance centrality

Assess risk in context rather than by score alone. A vulnerable WAF, email gateway, or security management appliance can provide an attacker with privileged network positioning and access to sensitive traffic or stored messages. CISA KEV status is therefore a more urgent operational signal than the distinction between the reported 7.2 and 8.6 scores.

Exploitation Status

Exploitation in the wild is confirmed by CISA’s inclusion of CVE-2026-111560 in the Known Exploited Vulnerabilities catalog. CISA added the entry on November 10, 2026, with a federal remediation due date of November 13, 2026. Organizations should assume that vulnerable, reachable appliances are targets and prioritize them over ordinary patch-cycle work.

CISA lists ransomware use as unknown. That field does not contradict confirmed exploitation; it means CISA has not attributed exploitation of this CVE specifically to ransomware campaigns. The available primary-source material also does not establish a named threat actor or a particular campaign.

A complete public proof-of-concept exploit was not confirmed in the retrieved primary-source material. Public technical research discusses the vulnerability and Barracuda firmware differences, and a Mandiant vulnerability disclosure is available, but defenders should distinguish research or advisory content from a tested public exploit. The absence of a retrieved PoC is not a reason to delay remediation because real-world exploitation is already confirmed.

Sources

The following sources support the vulnerability status, affected products, exploitation status, and remediation guidance:

  1. NVD: CVE-2026-111560
    NVD record, publication details, vulnerability description, and CVSS base score.

  2. CISA Known Exploited Vulnerabilities Catalog
    KEV inclusion, November 10, 2026 addition date, November 13, 2026 due date, and ransomware-use status.

  3. Barracuda security advisory
    Vendor remediation guidance, affected product families, fixed versions, and product-specific patch information.

  4. Mandiant vulnerability disclosure, MNDT-2026-0041
    Public vulnerability disclosure and related technical context.

  5. Brandefense CVE-2026-111560 summary
    Secondary affected-version and remediation reference.

  6. Beazley Security Labs advisory
    Additional technical research and analysis.

  7. watchTowr technical research
    Secondary research concerning Barracuda vulnerability behavior and related analysis.

The vendor advisory remains the authoritative source for selecting the correct firmware branch, patch identifier, upgrade procedure, and any product-specific workaround.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

ResponderRunbook · act now

Detection Guidance

Detection should combine asset inventory, administrative activity, configuration changes, and process telemetry. The vulnerable action may begin as a legitimate administrative configuration change, so a single event should not be treated as proof of compromise. Suspicious combinations include an unexpected timezone change followed by shell execution, outbound connections from the appliance, new local accounts, altered startup configuration, or configuration changes outside an approved maintenance window.

Prioritize systems that were internet-exposed, had administrative interfaces reachable from broad internal networks, or showed unexpected administrator logins. Preserve logs before rebooting or factory-resetting an appliance. Appliance logging depth varies by product and firmware, so the absence of shell telemetry does not demonstrate that exploitation did not occur.

Technical Notes

Search centralized logs and SIEM data for timezone changes followed by unusual process or network activity. Field names vary, but searches can use normalized concepts such as:

index=barracuda
(
  "timezone" OR "time zone" OR "timezone configuration"
)
| transaction host maxspan=30m
| search (
    "admin" OR "administrator"
  )
| table _time host user src_ip action message

For products that export audit events as JSON, an equivalent detection logic is:

event.product = "Barracuda"
AND event.action IN ("timezone_change", "configuration_change")
AND event.field IN ("timezone", "time_zone")
AND (
  process.name IN ("sh", "bash", "dash", "busybox")
  OR network.direction = "outbound"
  OR user.account_created = true
)

These queries are detection patterns, not vendor-confirmed event schemas. Adapt field names to the appliance’s exported logs and validate them against known-good administrative changes. Also review:

  • Authentication successes and failures for privileged accounts
  • Source IPs and geographies associated with administrator sessions
  • Configuration changes outside change windows
  • New or modified local users, SSH keys, scheduled tasks, and startup entries
  • Unexpected DNS, HTTP, HTTPS, SMTP, or other outbound connections
  • Firmware, patch, and support-access events
  • Any process or system logs showing shell commands executed by appliance services

If compromise is suspected, retain a forensic image or vendor-approved diagnostic bundle before remediation where feasible. Coordinate with Barracuda support or qualified incident responders because appliance-specific collection procedures may be required.

Remediation Steps

Upgrade every affected appliance to the appropriate fixed version and apply the product-specific patch where required:

  • ESG: upgrade to 9.4.0.030 or later; use BNSF-40425 for firmware 9.4.017 and later or BNSF-40430 for earlier firmware, as applicable.
  • ADC: upgrade to 6.4.0 and apply BNADC-16586 where required.
  • WAF: upgrade to 11.0.1 and apply BNADC-16586 where required.
  • WSG: upgrade to 16.1.100.100 and apply BNYF-24789.
  • BMA: upgrade to 5.5.4.0 and apply BNMA-32468.
  • WCC: upgrade to 2.2.1 and apply BNWF-60060.

Use Barracuda’s support portal and current product-specific instructions to obtain the correct firmware package and patch. The following command illustrates a verification workflow, not a universal Barracuda CLI command:

# Run through your approved management or automation interface.
# Replace the placeholders with the vendor-documented commands for the product.
barracuda-cli firmware show
barracuda-cli patch list
barracuda-cli patch install <vendor-patch-identifier>
barracuda-cli firmware show
barracuda-cli patch list

Do not execute those command names blindly on production appliances. Barracuda product families may use different management interfaces, and the vendor’s documented upgrade mechanism is authoritative. Record the pre-update firmware, patch identifier, maintenance window, backup status, and post-update verification.

If immediate patching is impossible, restrict management access to approved administrator networks, remove direct internet exposure, enforce multi-factor authentication where supported, disable unnecessary remote administration, and review firewall rules. These are temporary risk-reduction measures, not substitutes for upgrading. Barracuda’s instructions should govern any product-specific workaround, and the appliance should be discontinued or isolated if no supported mitigation is available.

Because the CVE is KEV-listed, remediation should include compromise assessment:

  1. Identify all instances and compare versions with the fixed releases.
  2. Prioritize internet-exposed and broadly reachable management interfaces.
  3. Review privileged authentication and configuration-change logs.
  4. Preserve evidence where suspicious activity is identified.
  5. Rotate appliance, administrator, API, service, and integration credentials if compromise is plausible.
  6. Check connected systems for follow-on access or unusual traffic.
  7. Upgrade, verify, and document the final patch state.
  8. Continue monitoring for post-remediation activity.

Patch reachable, unpatched appliances first, then use the same maintenance window to review privileged access and configuration-change history. If those checks uncover suspicious activity, preserve evidence and rotate relevant credentials before returning the system to normal operation.

Choosing a tool? Pricing and head-to-head guides

Last verified: 2026-11-16

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.