CVE-2026-111560: Barracuda appliance timezone command injection — now on CISA's KEV with a November 13 patch deadline

Authenticated admin command injection to root across six Barracuda appliances, chainable with a pre-auth bypass; KEV-listed with actions due November 13.
CoeLab Real-World Impact: 92/100 — Urgent. Editorial score v1.0. Evidence checked 2026-11-11T16:10:42.245466+00:00. CVSS and EPSS are separate measures, not this editorial score.
Rating breakdown: exploitation: 30, reachability: 20, consequences: 22, operational relevance: 20.
Who is affected
CVE-2026-111560 is a command injection flaw in the timezone configuration field of Barracuda appliance products that share a common codebase. Because that code is used across multiple product lines, a single bug touches six of them: Email Security Gateway (ESG) versions up to and including 9.4.0.27, Load Balancer Application Delivery Controller (ADC) up to and including 6.4.0, Web Application Firewall (WAF) up to and including 11.0.1, Web Security Gateway (WSG) up to and including 16.1.100.100, Message Archiver (BMA) up to and including 5.5.4.0, and WAF Control Center (WCC) up to and including 2.2.1.
The practical consequence of a shared-code flaw is that you cannot reason about exposure from your ESG inventory alone. Any unpatched Barracuda appliance in the listed families should be treated as potentially affected. Note that this command injection is not the same issue as CVE-2026-116606, the pre-authentication authorization bypass disclosed in the same advisory; only ESG is affected by that companion bug, but the two are most dangerous when combined.
If your appliances run current firmware with all recent patches applied — Barracuda released the fixes as part of its standard patch stream, and ESG firmware 9.4.0.17 and later carries one of the two published patches — you are not affected. Older builds that were never updated, including appliances still running builds predating the October disclosure window, need review regardless of whether they face the internet.
Real-world impact and exploitation evidence
Successful command injection in the timezone field lets an authenticated administrator inject shell metacharacters whose commands execute with root privileges once the crafted value is processed. Root execution on a security appliance is close to a worst-case outcome: these devices sit on the mail boundary or in front of web applications, terminate traffic, and hold credentials and keys. Root access enables persistence, tampering with traffic inspection, and lateral movement into the networks the appliance fronts.
CISA added CVE-2026-111560 to the Known Exploited Vulnerabilities catalog on November 10, 2026, and Barracuda's advisory was updated on November 9 to state that exploitation activity has been observed affecting a small number of organizations. That combination — a federal catalog listing citing observed use plus vendor confirmation — is the strongest exploitation evidence a new CVE can carry. The KEV entry also notes the vulnerability can be chained with CVE-2026-116606.
The KEV addition matters even though the underlying CVE is only days old. For context, this is not an old bug with new labeling: it was reported to Mandiant on October 15, 2026, published on November 2, and within eight days was both KEV-listed and vendor-confirmed as exploited. The federal remediation due date for US civilian agencies is November 13, 2026 — two days after catalog inclusion, an unusually tight window reflecting how seriously the threat is being treated.
For weighting, the CoeLab Real-World Impact score for this CVE is 92 (Urgent). Exploitation contributes the full 30 points from the KEV listing; reachability contributes 20 from the network attack vector and low attack complexity; consequences contribute 22 from the 8.6 CVSS base score; operational relevance contributes 20 because these are security edge devices. This score is a newsroom prioritization heuristic, not CVSS or EPSS, and it says nothing about any particular organization's exposure. Its main limitations here: the operational-relevance term is a category match rather than a measured installed base, EPSS (currently about 1.1%, 65th percentile) is not what drove the score, and the score would remain high even against a hypothetical future where public exploitation slowed.
Attack prerequisites
For CVE-2026-111560 on its own, the attacker needs access to the product's administrative interface and valid administrative credentials. Barracuda's advisory is explicit that successful exploitation requires the attacker to have access to the admin UI; the CVSS vector confirms this with Privileges Required: High. That is a genuine barrier: an internet-facing appliance is very different from one whose management plane is only reachable internally.
The complicating factor is the companion vulnerability, CVE-2026-116606. Barracuda's November 5 advisory update changed the authentication picture for that bug: authentication is no longer required to exploit it, though the attacker does need the administrative UI to be reachable. An attacker who can reach the admin interface at all can potentially combine the pre-auth bypass with the command injection to reach root without holding valid administrative credentials.
This shifts the practical mitigation from patching alone to exposure reduction: the administrative interfaces of these appliances should never be reachable from the public internet. Organizations whose admin interfaces are already restricted to trusted internal networks have a materially smaller attack surface than those whose management planes face the web.
Actions and fixes
Barracuda has released patches for every affected product line. The published patch identifiers are: BNSF-40425 for ESG firmware 9.4.0.17 and later, BNSF-40430 for ESG builds older than 9.4.0.17, BNADC-16586 for both ADC and WAF, BNMA-32468 for Message Archiver, BNWF-60060 for WAF Control Center, and BNYF-24789 for Web Security Gateway.
In practice most devices will have received these fixes automatically if automatic patching was left enabled. Barracuda's own guidance is to verify that firmware is current and patches applied, apply the appropriate patch manually if it was not applied automatically, and re-enable automatic patching if it was disabled. Devices several versions out of date may need sequential updates; Barracuda points to its Campus documentation for manual patching procedure and to support for help with multi-step upgrades.
Whether or not patching is immediate in your environment, restrict access to administrative interfaces to trusted internal networks using firewall rules or access controls. Given that the bundled pre-auth bypass turns network reachability of the admin UI into the main barrier to root compromise, this is not optional hardening — it is the control that degrades the realistic attack path.
Because exploitation has already been observed, patching alone is not forensically sufficient for organizations that find affected systems. CISA's KEV entry flags this vulnerability for forensic triage. If an affected appliance was unpatched while its admin interface was exposed, review device logs, look for unexpected account or timezone configuration changes, and involve incident response rather than treating the patch as closure.
Uncertainty and what could change
The vendor's exploitation statement is deliberately narrow — the small number of exploited organizations has not been quantified, no adversary attribution is published, and it is not known whether exploitation observed so far relied on the chained path or on leaked/stolen administrative credentials. Neither CISA's entry nor Mandiant's disclosure identifies a specific threat actor or a specific victim.
EPSS currently reads around 1.1% for this CVE with a modest percentile, which underscores two separate things: the probability model and the CISA catalog can disagree, and the catalog's direct exploitation reports are the more immediate signal here. EPSS is a statistical estimate of near-term exploitation likelihood in the wild, not a statement about this adversary's current activity. If EPSS shifts upward in coming days, it will confirm rather than change this assessment.
The KEV entry has no ransomware association recorded and no public exploit has been confirmed in the sources reviewed. However, the tight KEV due date signals that CISA expects practical exploitation; there is no evidence this has peaked. Barracuda has updated the advisory at least twice since disclosure and may again. If Barracuda retracts, revises patches, or expands the affected-version list, the practical guidance above would need revision.
Sources and evidence date
Vendor evidence comes from Barracuda's Trust Center advisory covering both CVE-2026-116606 and CVE-2026-111560, last seen showing an update of November 9, 2026 at 9:00pm EST. Researcher-side evidence comes from Mandiant's public disclosure record MNDT-2026-0041, which documents reporting to Mandiant on October 15, 2026 and publication on November 2, 2026, alongside the affected-version list and CVSS vector. Federal evidence comes from CISA's Known Exploited Vulnerabilities catalog entry added November 10, 2026.
Version boundaries cited are those published in the affected products and remediation table of the vendor advisory and are identical in the Mandiant record and the CVE record as reviewed; both list the ESG patch stream rather than a single fixed-version number, so 'fixed' status for ESG is expressed through firmware 9.4.0.17 and later plus the two patch identifiers. This article reflects evidence as reviewed on November 11, 2026; the CVE record itself was last updated November 3, 2026.
No exploit code, weaponized payload, or step-by-step exploitation guidance exists in the reviewed public sources, and none is reproduced here.
Primary-source links
https://trust.barracuda.com/security/pre-authentication-authorization-bypass-command-injection
https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0041.md
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-111560
https://www.cve.org/CVERecord?id=CVE-2026-111560
AI-assisted research and drafting, with a separate model editorial review. CoeLab ratings are editorial judgments, not a substitute for checking your own versions and vendor advisories. Methodology: https://thecoelab.com/blog/security/methodology
Related Posts
Your USB-C Dock Is Part of Your Network. Test It That Way.
A trending Ethernet investigation shows why docks belong in your network diagram. Here is how to isolate bottlenecks before replacing routers or adapters.
CVE-2026-129448: Apache Roller XML-RPC deserialization gets CISA KEV deadline — unauthenticated remote code execution in versions before 6.1.5
Apache Roller before 6.1.5 runs unauthenticated XML-RPC deserialization before authentication; it is now on CISA's exploited list with a patch deadline of November 23, 2026.
Valkey’s Sorted Set Upgrade Is a Capacity Planning Opportunity
Valkey’s sorted set redesign promises lower index overhead. Here is how to test the real memory benefit, protect latency, and turn savings into usable capacity.