On this page (6 sections)
CISA has added CVE-2026-111560, an OS command injection flaw affecting several Barracuda Networks appliance products, to its Known Exploited Vulnerabilities (KEV) catalog on 2026-11-10. According to the NVD entry, an authenticated administrator can inject commands through the timezone setting, and those commands run with root privileges.
If your organization runs a Barracuda email gateway, load balancer, web application firewall or related appliance, this is worth checking today. Federal agencies were given a short deadline, and the KEV listing signals that exploitation has been observed. The public record is thin on some details, so this article separates what is confirmed from what is not.
What happened
The NVD description says the listed Barracuda products contain an OS command injection vulnerability. The CVE record was published on 2026-11-02, and CISA added it to KEV on 2026-11-10 with a due date of 2026-11-13. CISA's required action is to apply mitigations following vendor instructions, or to discontinue use of the product if mitigations are not available.
The sources do not say who is exploiting the flaw, how many devices are affected, or whether ransomware groups are involved. CISA lists ransomware use as "Unknown". Treat any claim beyond that as unconfirmed.
Technical details
The weakness class is CWE-78, improper neutralization of special elements in an OS command. In plain terms, the appliance takes a value from the timezone configuration field and later passes it to a system command without properly removing shell metacharacters. A specially crafted value can therefore add extra commands, and they run as root when the value is processed, according to the GitHub advisory.
The CVSS v4 metrics in that advisory describe a network attack vector, low attack complexity, no user interaction and high impact on confidentiality, integrity and availability. The important qualifier is that privileges required are high: the attacker needs an authenticated administrator session first.
Why the admin requirement does not make this safe
NVD notes that this vulnerability can be chained with CVE-2026-116606. The sources provided do not describe that second flaw, so how the chain works is not confirmed here. The reference URL for the Barracuda advisory is titled "pre-authentication authorization bypass command injection", which suggests an attacker may be able to reach the administrator step without valid credentials. That is an inference from the page address only, so read the vendor advisory for the actual details.
Even without a chain, stolen or reused admin credentials, or an exposed management interface, would be enough to reach the vulnerable field. Root access on a mail or web gateway means an attacker could read or alter traffic the device handles.
Who is affected
NVD lists these products as affected:
- Email Security Gateway (ESG)
- Load Balancer
- Application Delivery Controller (ADC)
- Message Archiver (BMA)
- WAF Control Center (WCC)
- Web Application Firewall (WAF)
- Web Security Gateway (WSG)
The GitHub advisory says "certain Barracuda appliance products using common Barracuda code", and lists affected and patched versions as unknown. Do not assume a product or firmware release is safe because it is not named in a version list. Confirm against Barracuda's security advisory and the Mandiant disclosure referenced by the CVE record. This article could not confirm what those pages say.
What to do now
- Make a list of every Barracuda appliance you run and note the product and firmware version from its admin interface.
- Open the Barracuda security advisory linked above and follow its mitigation or firmware instructions for each product.
- Restrict the management interface to a trusted internal network or VPN. It should not be reachable from the internet.
- Rotate all administrator passwords and API keys on the appliances, and enable multi-factor authentication if the product supports it.
- Review administrator accounts and remove any you do not recognize.
- Check the timezone setting and recent configuration changes for unexpected or unusual values.
- Review admin login and audit logs since at least 2026-11-02 for unfamiliar sources or times.
- If you cannot apply mitigations, follow CISA's guidance, which includes discontinuing use of the product.
If you find signs of compromise, treat the appliance as fully compromised, because the commands run as root. Preserve logs, isolate the device, and rebuild from a trusted image rather than trying to clean it. Our guide on what to do when a website is hacked covers the general response steps.
Detection and monitoring
Because the flaw sits behind an authenticated admin function, the most useful signals are in the appliance's own logs and in your network. Look for configuration changes to the timezone field made outside a change window, administrator logins from unfamiliar addresses, and outbound connections from the appliance to hosts you do not recognize.
Forward appliance logs to a central system so an attacker with root cannot erase the only copy. Alert on new admin accounts and on changes to the management interface exposure.
For the websites and services behind these devices, outside-in checks help you notice side effects such as unexpected certificate, DNS or header changes. Webforta Monitor tracks those changes, though it does not detect this vulnerability itself. You can also review what outside-in tools can and cannot see in our malware detection overview.
Timeline
| Date | Event |
|---|---|
| 2026-11-02 | CVE-2026-111560 published to NVD and the GitHub Advisory Database |
| 2026-11-10 | Added to the CISA KEV catalog |
| 2026-11-13 | CISA KEV due date for required action |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
