What happened with the Barracuda ESG vulnerabilities?
On November 10, 2026, CISA added two Barracuda vulnerabilities to its Known Exploited Vulnerabilities catalog: CVE-2026-116606, an Email Security Gateway (ESG) authentication bypass using an alternate path or channel, and CVE-2026-111560, an OS command injection across multiple Barracuda products. CISA set a November 13 due date for federal civilian agencies.
Chained together, the bypass gets an attacker past authentication and the command injection runs commands on the appliance. Barracuda's fixed builds and per-product patches are listed in its security advisories.
Which Barracuda products are affected?
- CVE-2026-116606: Barracuda Email Security Gateway (ESG).
- CVE-2026-111560: multiple Barracuda products, per CISA's KEV entry. Barracuda's advisory lists each affected product and its patch.
How to check if you're affected
- Inventory every Barracuda ESG appliance and other Barracuda product you run, including virtual appliances.
- Compare each appliance's firmware and patch level with the fixed builds in Barracuda's advisory.
- Check whether the management interface is reachable from the internet or from untrusted networks.
What to do now
- Apply Barracuda's patches for both CVEs on every affected product. CISA's required action is to follow vendor instructions or stop using the product if no mitigation is available.
- Restrict the management interface to trusted internal networks.
- Review appliance logs and configuration for changes you didn't make since early November.
Why an authentication bypass plus command injection is so dangerous
Each flaw alone is limited. A command injection that needs an admin login is only reachable by admins, and an authentication bypass that only reaches a settings page does little damage. Chained, the bypass delivers an unauthenticated attacker to the one function that passes input to the operating system. The same pattern shows up in web applications: an alternate route that skips the login check, such as a legacy endpoint or a management API, plus one function that builds a shell command from user input. Look for both halves in your own code, because fixing either one breaks the chain.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify's code analysis looks for authentication and authorization failures, including privilege escalation and business-logic flaws, on every pull request, and the AI pentest agent tests authenticated REST and GraphQL API flows. This is about the same class of bug in your code, not the vendor's.
Patching the appliance is IT's job. The bug class, an authentication bypass reached through an alternate path, is the part to look for in your own code.
Frequently Asked Questions
Which Barracuda vulnerabilities are being exploited?
CVE-2026-116606, an authentication bypass in the Barracuda Email Security Gateway, and CVE-2026-111560, an OS command injection in multiple Barracuda products. CISA added both to its Known Exploited Vulnerabilities catalog on November 10, 2026.
What is the CISA deadline for the Barracuda ESG flaws?
CISA set November 13, 2026 as the due date for US federal civilian agencies. Other organizations aren't bound by it, but a three-day deadline signals active exploitation and high urgency.
How do I protect a Barracuda ESG appliance?
Apply Barracuda's fixed builds for both CVEs, then limit the management interface to trusted internal networks. Review the appliance's configuration and logs for changes you didn't make.
Update Log
- Nov 17, 2026: page published from the CISA KEV catalog entries for both CVEs.