> ## Content Index
> Fetch the complete content index at: https://f4n6.co.uk/llms.txt
> Use this file to discover other available public pages before exploring further.

# Barracuda OS command injection CVE-2026-111560 added to CISA KEV
- URL: https://f4n6.co.uk/security-feed/barracuda-os-command-injection-cve-2026-111560-added-to-cisa-kev/
- Published: 2026-11-10T22:03:29.000Z
- Updated: 2026-11-10T22:03:29.000Z
- Author: Jeff Davies
- Tags: #security-feed, CVE-2026-111560, CVE-2026-116606

## 1\. Executive summary

CISA added CVE-2026-111560 (CVSS 8.6 HIGH, CWE-78 OS command injection) to the Known Exploited Vulnerabilities catalog on 2026-11-10, alongside CVE-2026-116606 (CVSS 9.3 CRITICAL, CWE-288 authentication bypass), the flaw it is designed to chain with. Barracuda states it has identified exploitation activity affecting a small number of organizations, and the two flaws together let an unauthenticated attacker bypass authorization and reach root on Email Security Gateway and several other Barracuda appliances. The exposure for EMEA financial services is concentrated at the network edge: any ESG, ADC, BMA, WAF, WCC or WSG with its administrative interface reachable from the internet is a candidate, and the KEV remediation due date is 2026-11-13\. Barracuda says it released patches for affected products; the specific fixed versions are not stated in the reporting available here.

## 2\. Regulatory framing

| Article      | Trigger (the fact in this item)                                                                                                                                                     | Practical impact                                                                                                                  |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| DORA Art. 17 | Barracuda reports identified exploitation activity against a small number of organizations, so an affected client has an ICT-related incident to manage, not only a patch to apply. | The incident management process must cover detection, containment and root-cause handling for the appliance, not just the update. |
| DORA Art. 19 | The same confirmed exploitation activity, where it hits an entity in DORA scope and meets the major-incident threshold, is a reportable event.                                      | Major ICT-related incidents must be reported to the competent authority under the client's classification outcome.                |
| NIS2 Art. 23 | Confirmed exploitation of an internet-facing appliance is a significant incident for entities in NIS2 scope.                                                                        | Incident reporting obligations to the CSIRT or competent authority are engaged where the significance threshold is met.           |

## 3\. Technical analysis & attack chain

The two CVEs are a chain. CVE-2026-116606 gets an unauthenticated attacker past authentication on the ESG; CVE-2026-111560 turns that foothold into root. Barracuda's own wording, quoted by The Register, is that exploited in combination they "could allow an attacker to bypass authorization controls and obtain root access to the device."

1. The attacker reaches the ESG administrative user interface. Authentication is not required to exploit CVE-2026-116606, but the attacker must have access to that admin UI, which is why an internet-facing management interface is the precondition for the chain.
2. The attacker invokes a configuration-import function through an alternate path or channel (CWE-288), bypassing authorization.
3. The attacker restores a crafted, compatible backup archive through that import function, which modifies the appliance's global configuration without authorization.
4. The modified configuration carries a crafted timezone value. When that value is subsequently processed, the OS command injection in CVE-2026-111560 executes the injected commands with root privileges.

The command-injection flaw is not ESG-only. CVE-2026-111560 affects Barracuda 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 injection requires an authenticated administrator to set the crafted timezone value, which is why the authentication bypass in CVE-2026-116606 is what makes the pair dangerous from an unauthenticated position. CVE-2026-116606 is scoped to ESG.

Barracuda disclosed and fixed both vulnerabilities in the week before 2026-11-10 and warned on November 2 that the combination could yield root; at that point it reported no active exploitation. In a late Monday update it said: "We have identified exploitation activity affecting a small number of organizations." It has not said how many organizations were hit, who is responsible, or whether the intruders obtained root. The Register reports those gaps directly and Barracuda declined to answer its questions on victim count.

What root on these appliances would permit is stated by The Register as a consequence, not an observation: data theft, backdoor installation and full control of affected systems. No source here reports any of that as having occurred in this campaign. No malware family, command-and-control infrastructure, persistence mechanism, lateral-movement technique or exfiltration detail is given in the available reporting, so none is asserted.

Attribution is unconfirmed. The Register notes that edge-device exploits of this kind have been used by Chinese-government spies and that in 2023 the FBI blamed PRC-linked attackers for attacks on Barracuda ESGs, but it explicitly says who is responsible for these attacks is not yet known. That 2023 history is background, not a link to this campaign, and no MITRE ATT&CK profile ties a named actor to CVE-2026-111560 or CVE-2026-116606.

One discrepancy to record: The Register describes CVE-2026-116606 as a "pre-authentication authorization bypass" while NVD classifies it as CWE-288, authentication bypass using an alternate path or channel. Both describe the same flaw; the verified classification is CWE-288.

## 4\. Mitigation & containment

### P1 (within 24 hours)

- Close administrative interfaces on ESG, ADC, BMA, WAF, WCC and WSG to the internet. Restrict admin UI access to a management network or named source addresses. This is the precondition for the CVE-2026-116606 chain and the single highest-value control while patching completes.
- Apply the Barracuda patches for both CVE-2026-116606 and CVE-2026-111560\. Barracuda states it released patches for affected products; the fixed version numbers are not stated in the reporting available here, so confirm the target release against Barracuda's own advisory before scheduling.
- Treat the 2026-11-13 KEV due date as the deadline for both CVEs.
- Hunt for unauthorized configuration changes on ESG appliances, in particular restored backup archives and altered global configuration, and for unexpected timezone values. A changed timezone setting is the observable precursor to the CVE-2026-111560 injection.

### P2 (within 72 hours)

- Where an ESG was internet-exposed with its admin UI reachable and patching cannot be confirmed as having preceded exposure, treat the appliance as potentially compromised: review configuration against a known-good baseline, check for backup archives that were not imported by an administrator, and rotate credentials and any secrets held in the appliance configuration.
- Inventory every Barracuda product in the affected list, not only ESG. The command-injection flaw spans ADC, BMA, WAF, WCC and WSG as well.

### P3 (within 7 days)

- Add the behavioural detections in §6 to monitoring for the Barracuda estate.
- Confirm third-party and managed-service providers running Barracuda appliances on your behalf have applied the patches, and record their confirmation against your ICT third-party register.

No fixed release identifier, patch filename or KB number is given in the sources here; do not assume one.

## 5\. Indicators of compromise

No indicators of compromise available in the source material.

The reporting names no hashes, domains, IP addresses, filenames or command strings. The observable signals are behavioural, not atomic.

### Behavioural indicators

| behaviour                                                            | where to observe                                            | confidence                                                                                      |
| -------------------------------------------------------------------- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Configuration-import function invoked on ESG outside a change window | ESG administrative audit logs and configuration-change logs | Medium; derived from the CVE-2026-116606 mechanism, single-sourced to NVD and The Register      |
| Backup archive restored that no administrator scheduled              | ESG configuration and import logs                           | Medium; same basis                                                                              |
| Timezone value changed to an unexpected or malformed string          | ESG global configuration and change history                 | Medium; the injection fires when the crafted timezone value is processed                        |
| Root-level command execution following a configuration import        | ESG process execution and system logs                       | Low; the chain's end state is described by Barracuda as possible, not observed in the reporting |

## 6\. Detection

Insufficient indicators to author detection rules.

The sources describe the mechanism (a crafted timezone value processed after a configuration import) but give no command string, filename, path, registry key or other artefact that would appear in the malicious input. A rule built on the CVE identifiers or product names would detect reporting about the flaw, not exploitation of it. Detection should instead rest on the behavioural signals in §5: alert on configuration imports and timezone changes on Barracuda appliances that fall outside approved change activity, and on root-level process execution on the appliance that does not match its baseline.

## CVE assessment

2 referenced CVEs — **2 actively exploited (CISA KEV)**, 1 critical (CVSS ≥ 9.0)

| CVE                                                                                | CVSS         | Exploited        | EPSS | Summary                                                                                                                          |
| ---------------------------------------------------------------------------------- | ------------ | ---------------- | ---- | -------------------------------------------------------------------------------------------------------------------------------- |
| [CVE-2026-116606](https://nvd.nist.gov/vuln/detail/CVE-2026-116606?ref=f4n6.co.uk) | 9.3 Critical | ⚠ KEV 2026-11-10 | 2%   | An authentication bypass in Barracuda Email Security Gateway versions earlier than 9.4.0.030 allows an unauthenticated remote a… |
| [CVE-2026-111560](https://nvd.nist.gov/vuln/detail/CVE-2026-111560?ref=f4n6.co.uk) | 8.6 High     | ⚠ KEV 2026-11-10 | 1%   | Improper neutralization of shell metacharacters in the timezone configuration field in certain Barracuda appliance products usi… |

## 7\. Sources

- NVD, CVE-2026-111560 detail, https://nvd.nist.gov/vuln/detail/CVE-2026-111560, 2026-11-10
- NVD, CVE-2026-116606 detail (CISA KEV entry), https://nvd.nist.gov/vuln/detail/CVE-2026-116606
- The Register, "Barracuda's email security gateways bitten by make-me-root vulns", https://www.theregister.com/security/2026/11/10/barracudas-email-security-gateways-bitten-by-make-me-root-vulns/5308883, 2026-11-10

## 8\. Adverse Trace position

Adverse Trace assesses CVE-2026-111560 at CVSS 8.6 HIGH and CVE-2026-116606 at CVSS 9.3 CRITICAL, both in CISA KEV with a 2026-11-13 remediation due date, and treats the pair as one exposure because neither is exploited to root without the other. The client impact is bounded by where Barracuda appliances sit: an ESG with an internet-facing admin UI is the priority, and the other affected products carry the command-injection flaw without the documented pre-authentication path. Confirmed exploitation is Barracuda's own statement, single-sourced to the vendor and relayed by The Register; the victim count, the actor and whether root was obtained are all unstated, and we will not fill those gaps. We will track Barracuda's advisory for fixed version numbers and any expansion of the exploitation statement, and we will update this note if either changes. Clients should confirm patch status and admin-UI exposure for every Barracuda product in the affected list and report back before the KEV due date.

---

[Read the original source →](https://nvd.nist.gov/vuln/detail/CVE-2026-111560?ref=f4n6.co.uk)

*Published via PulseTrace — Adverse Trace threat intelligence.*