All articles

NewsNovember 10, 20264 min read

Barracuda: CVE-2026-111560 exploited, added to CISA KEV

CISA confirms exploitation of the Barracuda timezone command injection (CVE-2026-111560): root on several appliances, US deadline 13 November.

Glowing Information Security lettering on a dark digital background

On 10 November 2026 the US agency CISA added CVE-2026-111560 to its Known Exploited Vulnerabilities (KEV) catalog. It is the command injection in the timezone setting found in several Barracuda appliances. Inclusion in the catalog means CISA has evidence that the flaw is being exploited in real attacks. This is what is new compared with our article of 2 November, when neither Barracuda nor Mandiant reported any ongoing attacks.

This article is based on a single source: CISA’s KEV entry, together with data from the National Vulnerability Database (NVD). The entry does not say who is exploiting the flaw, against which products or with which techniques.

What the KEV entry says

  • Name: Barracuda Networks Multiple Products OS Command Injection Vulnerability.
  • Added to the catalog: 10 November 2026.
  • Deadline for US federal agencies: 13 November 2026, only three days later.
  • Known use in ransomware campaigns: unknown («Unknown»).
  • Required action: apply mitigations in accordance with the vendor’s instructions, in compliance with CISA’s BOD 26-04 directive on prioritising security updates based on risk and with its «Forensics Triage Requirements»; for cloud services, follow the same directive, or discontinue use of the product if mitigations are unavailable. CISA also asks organisations to evaluate the internet exposure of each asset.

So, alongside patching, CISA points to its forensic triage requirements: besides fixing the flaw, you need to check whether the device has already been compromised.

Technical details

According to the description published by NVD, the defect is an improper neutralisation of shell metacharacters (CWE-78) in the timezone configuration field, in code shared by several Barracuda appliances. An authenticated administrator can enter a crafted value in the field: when the system processes it later, the commands it contains run with root privileges.

The CVSS 4.0 score assigned by Mandiant is 8.6 (high), with vector AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N: network attack, low complexity, no user interaction, but high privileges required. At the time of writing the NVD entry is still being analysed («Undergoing Analysis»), last modified on 11 November 2026.

Among its references the entry lists Mandiant advisory MNDT-2026-0041 and Barracuda’s advisory on the pre-authentication authorisation bypass and the command injection, the same ones we covered on 2 November.

In the MITRE ATT&CK model, running commands on the system falls under T1059.004 (Unix Shell).

The privilege question

The NVD description lists administrator access as a requirement, and the KEV entry does not explain how attackers obtained it. As we reported on 2 November, on the Email Security Gateway (ESG) the other flaw in the same advisory, CVE-2026-116606, lets an unauthenticated attacker modify the appliance configuration, and the two vulnerabilities can be chained all the way to root. The source of this article, however, only covers CVE-2026-111560 and does not say whether the chain was used in the attacks.

On the other products affected by the command injection (Web Application Firewall, WAF Control Center, Web Security Gateway, Message Archiver and Load Balancer ADC), the description still lists administrator access as a requirement.

What it means for European companies

The KEV catalog is binding only on US federal agencies, but it is widely used as a reference for prioritising updates. For organisations subject to NIS2 (in Italy, Legislative Decree 138/2024), which must manage vulnerabilities based on risk, a flaw with confirmed exploitation on email gateways, WAFs and email archives should be treated as top priority. In healthcare and in other sectors where email carries personal data, a compromise of these devices should also be assessed as a possible personal data breach under the GDPR.

What to do now

  1. Inventory: identify all Barracuda appliances of the six affected products, including virtual instances and those managed by service providers.
  2. Update: apply the fixes provided by Barracuda and check that they are actually installed. Affected versions and patch codes are in the table of our 2 November article.
  3. Management interface: if it is reachable from the internet, close it and make it accessible only from trusted management networks.
  4. Administrator accounts: check that there are no unknown users and, if the interface was exposed, change the administrator passwords.
  5. Hunt for compromise, as CISA requires with forensic triage: in the administrative logs, look for timezone changes with unusual values, configuration imports and backup restores, and check for unexpected outbound connections from the appliance.
  6. Updating does not remove access an attacker has already gained: if you see suspicious signs, contact Barracuda support.

How ARXDOME helps

ARX Expose shows which of your company’s services are visible from the internet, and ARX Scout, with your authorisation, checks the ports and services of your public addresses first-hand; with ARX Scout Assessment it also flags exposed administration panels. ARX Radar shows, from your firewall logs, who is attacking your perimeter right now.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles