The Barracuda Email Security Gateway is under active attack through a two flaw exploit chain, CVE-2026-116606 and CVE-2026-111560, that hands an unauthenticated attacker root on the appliance. Barracuda confirmed attacks on November 9, and CISA added both flaws to its catalog on November 10. Upgrade every ESG to 9.4.0.030 now.
What Is the Barracuda Email Security Gateway Exploit Chain?
Two flaws combine into one critical problem. First, CVE-2026-116606 is an unauthenticated authorization bypass that an attacker triggers through a crafted configuration backup restore, rated 9.8 on CVSS v3 and 9.3 on CVSS v4. Second, CVE-2026-111560 is a command injection flaw rated 8.6 that normally needs an admin login. Chained together, they give an attacker root on the Barracuda Email Security Gateway straight from the admin web interface, with no credentials at all.
How Does the Exploit Chain Reach Root on the ESG?
The sequence is short and reliable. An attacker uploads a crafted configuration backup to restore, which trips the authorization bypass and grants access the login should have blocked. Then the attacker reaches the command injection flaw through the admin web interface and runs commands as root. As a result, a single request path turns an internet facing Barracuda Email Security Gateway into attacker controlled infrastructure.
Which Barracuda Email Security Gateway Versions and Products Are at Risk?
For the full unauthenticated chain, the exposure sits in Barracuda Email Security Gateway releases before 9.4.0.030. However, the command injection flaw reaches further on its own. With an admin login, CVE-2026-111560 also affects five more Barracuda products, so patch them on the same clock.
| Item | Detail |
|---|---|
| CVEs | CVE-2026-116606 and CVE-2026-111560 |
| CVE-2026-116606 | Unauthenticated authorization bypass via crafted config backup restore, CVSS v3 9.8, v4 9.3 |
| CVE-2026-111560 | Command injection, needs an admin login, CVSS 8.6 |
| Chained impact | Unauthenticated root on the ESG from the admin web interface |
| Affected (full chain) | Barracuda Email Security Gateway before 9.4.0.030 |
| CVE-2026-111560 also hits | WAF, Load Balancer ADC, Message Archiver, WAF Control Center, Web Security Gateway |
| Fix | Barracuda ESG 9.4.0.030 |
| Exploitation | Barracuda confirmed attacks November 9, public proof of concept since November 3 |
| CISA KEV | Added November 10, 2026, federal deadline November 13 |
Confirm the fixed build and the product list in the official Barracuda security advisory, and the catalog entries in the CISA Known Exploited Vulnerabilities catalog.
Are Attackers Exploiting the Barracuda Email Security Gateway Flaws?
Yes, and the timeline is tight. A public proof of concept has circulated since November 3, Barracuda confirmed real attacks on November 9, and CISA added both CVEs to its catalog on November 10 with a federal remediation deadline of November 13. You can read the CISA alert on the additions for the official record. In short, the gap between a public exploit and confirmed attacks was less than a week.
How Strong Is the Evidence Behind the Barracuda Email Security Gateway Chain?
We separate confirmed facts from single reports, so you can judge the risk yourself.
- Confirmed by Barracuda: both flaws, their types, the affected products, the 9.4.0.030 fix, and the attacks observed on November 9
- Confirmed by CISA: the November 10 catalog addition and the November 13 federal deadline
- Reported, not confirmed by us: the public proof of concept dated November 3, and the exact request sequence used in the attacks
- Still open: the scale of exploitation, and whether attackers are using the command injection flaw on its own against the other five Barracuda products
How Do You Fix and Check the Barracuda Email Security Gateway?
Patching is step one, not the finish line, because the chain reaches root. Work through these steps on every Barracuda Email Security Gateway and the other affected products.
- Upgrade first: move every ESG to 9.4.0.030 or later, and patch the five other products that the command injection flaw affects
- Restrict the admin interface: keep the management web interface off the public internet and limit it to trusted addresses
- Assume compromise on exposed units: if an appliance faced the internet before the patch, treat it as potentially breached
- Rotate secrets: reset appliance credentials, API keys and any integrated account the device could reach, because root access exposes them all
- Review configuration and logs: check for unexpected configuration restores, new accounts, and command execution from the web user
What Should Your Team Do About the Barracuda Email Security Gateway Now?
Edge security appliances concentrate access, so attackers reach them first. Our 2026 Mid Year Threat Pattern Report found that attackers weaponized eight of eleven zero days, or 73 percent, within 72 hours of disclosure, and this chain moved even faster. Therefore, upgrade today and fold the forensic review into the same change window.
Above all, prove the appliance is clean rather than assume it. Our team runs penetration testing and vulnerability assessments that show what an attacker can reach through your Barracuda Email Security Gateway, and our PTaaS platform keeps that testing running between audits.
Key Takeaways
- CVE-2026-116606 and CVE-2026-111560 chain into unauthenticated root on a Barracuda Email Security Gateway from the admin web interface
- The full chain affects ESG before 9.4.0.030, and the command injection flaw alone affects five more Barracuda products
- Barracuda confirmed attacks on November 9, a public proof of concept has circulated since November 3, and CISA set a November 13 deadline
- Upgrade every ESG to 9.4.0.030, then treat any internet facing appliance as potentially compromised
- Keep the admin web interface off the public internet, rotate secrets, and review configuration and logs after you patch
Frequently Asked Questions About the Barracuda Email Security Gateway Exploit
What is the Barracuda Email Security Gateway exploit chain?
It chains CVE-2026-116606, an unauthenticated authorization bypass, with CVE-2026-111560, a command injection flaw. Together they give an attacker root on a Barracuda Email Security Gateway from the admin web interface without any login.
Which Barracuda Email Security Gateway versions should you patch?
ESG releases before 9.4.0.030 carry the full unauthenticated chain. Barracuda fixed the flaws in 9.4.0.030, so upgrade every appliance to that build or later.
Are attackers exploiting the Barracuda flaws?
Yes. Barracuda confirmed attacks on the Barracuda Email Security Gateway on November 9, 2026, and a public proof of concept has circulated since November 3. CISA added both CVEs on November 10.
Does the flaw affect other Barracuda products besides the Email Security Gateway?
The command injection flaw CVE-2026-111560, which needs an admin login, also affects the Web Application Firewall, Load Balancer ADC, Message Archiver, WAF Control Center and Web Security Gateway. Only the Barracuda Email Security Gateway faces the full unauthenticated chain.
What is the federal deadline for the Barracuda Email Security Gateway CVEs?
CISA set a remediation deadline of November 13, 2026 when it added both flaws to its Known Exploited Vulnerabilities catalog on November 10. Confirm the date against the catalog entry.
Does patching the Barracuda Email Security Gateway close the incident?
Not on its own. Because the chain reaches root, treat a vulnerable appliance as potentially compromised, rotate its credentials, and review its configuration and logs after you upgrade to 9.4.0.030.

