{"id":4158,"date":"2026-11-11T07:08:22","date_gmt":"2026-11-11T15:08:22","guid":{"rendered":"https:\/\/cyber.mag212.com\/barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances\/"},"modified":"2026-11-11T07:10:21","modified_gmt":"2026-11-11T15:10:21","slug":"barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances","status":"publish","type":"post","link":"https:\/\/cyber.mag212.com\/fr\/barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances\/","title":{"rendered":"Barracuda\u2019s Exploited Flaw Chain Gives Attackers Root on Six Appliance Lines; CISA Sets a 13 November Deadline"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">If a Barracuda appliance\u2019s administrative interface can be reached from the internet, assume someone has already tried it. Two flaws disclosed on 2 November, an authorization bypass in Email Security Gateway and a command injection shared by six product lines, chain together to give an unauthenticated attacker root. Barracuda confirmed exploitation on 9 November, and CISA added both CVEs to its Known Exploited Vulnerabilities (KEV) catalog the next day with a three-day deadline and an explicit instruction to look for compromise, not just patch.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>CVEs<\/strong><\/td><td>CVE-2026-116606 (9.3) \u00b7 CVE-2026-111560 (8.6)<\/td><\/tr><tr><td><strong>Affected<\/strong><\/td><td>ESG, Load Balancer ADC, BMA, WCC, WAF, WSG<\/td><\/tr><tr><td><strong>Condition<\/strong><\/td><td>Admin UI reachable; no credentials<\/td><\/tr><tr><td><strong>IOCs<\/strong><\/td><td>None published<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">What happened<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>[Confirmed]<\/strong> Barracuda&#8217;s advisory covers an authorization bypass in <strong>Email Security Gateway only<\/strong> (CVE-2026-116606, CVSS 9.3) and a command injection in <strong>ESG, Load Balancer ADC, Message Archiver, WAF Control Center, WAF and Web Security Gateway<\/strong> (CVE-2026-111560, CVSS 8.6). Chained, they give root. On 9 November at 21:00 EST Barracuda added that it had seen exploitation &#8220;affecting a small number of organizations&#8221;. (<a href=\"https:\/\/trust.barracuda.com\/security\/pre-authentication-authorization-bypass-command-injection\" target=\"_blank\" rel=\"noopener\">Barracuda<\/a>) CISA added both to KEV on <strong>10 November<\/strong>, due <strong>13 November<\/strong>, with <strong>forensic triage &#8220;Yes&#8221;<\/strong>, ransomware use &#8220;Unknown&#8221; and references to Mandiant disclosures MNDT-2026-0041\/-0042. (<a href=\"https:\/\/raw.githubusercontent.com\/cisagov\/kev-data\/develop\/known_exploited_vulnerabilities.json\" target=\"_blank\" rel=\"noopener\">CISA KEV<\/a>)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>[Reported]<\/strong> Previdian saw 17 attempts against CVE-2026-116606 from 15 IP addresses in three countries between 9 and 11 November; the IPs weren&#8217;t published and the actors are unidentified. No ransomware link has been reported. (<a href=\"https:\/\/www.securityweek.com\/recently-patched-barracuda-vulnerabilities-exploited-in-attacks\/\" target=\"_blank\" rel=\"noopener\">SecurityWeek<\/a>) (<a href=\"https:\/\/previdian.com\/CVE-2026-116606\" target=\"_blank\" rel=\"noopener\">Previdian<\/a>)<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1600\" height=\"587\" src=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/01-barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances-diagram.jpg\" alt=\"Five-step chain from a reachable admin UI through CVE-2026-116606 config restore and a crafted timezone value to CVE-2026-111560 command injection and root; six affected Barracuda products below.\" class=\"wp-image-4157\" srcset=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/01-barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances-diagram.jpg 1600w, https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/01-barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances-diagram-300x110.jpg 300w, https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/01-barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances-diagram-1024x376.jpg 1024w, https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/01-barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances-diagram-768x282.jpg 768w, https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/01-barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances-diagram-1536x564.jpg 1536w, https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/01-barracuda-esg-cve-2026-116606-111560-exploited-root-six-appliances-diagram-18x7.jpg 18w\" sizes=\"auto, (max-width: 1600px) 100vw, 1600px\" \/><figcaption class=\"wp-element-caption\"><strong>Figure 1 \u00b7 The Barracuda chain, as MAG212 reads it.<\/strong> Two CVEs chained to root. The middle step is MAG212&#8217;s inference from CISA&#8217;s two KEV descriptions, not a published walkthrough. Below: the six affected product lines. Diagram: MAG212 CYBER<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Who is affected and how it works<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Product<\/th><th>CVE(s)<\/th><th>Patch ID<\/th><th>Product<\/th><th>CVE(s)<\/th><th>Patch ID<\/th><\/tr><\/thead><tbody><tr><td>ESG 9.4.017 and later<\/td><td>both<\/td><td><code>BNSF-40425<\/code><\/td><td>WAF Control Center<\/td><td>111560<\/td><td><code>BNWF-60060<\/code><\/td><\/tr><tr><td>ESG below 9.4.017<\/td><td>both<\/td><td><code>BNSF-40430<\/code><\/td><td>Web Application Firewall<\/td><td>111560<\/td><td><code>BNADC-16586<\/code><\/td><\/tr><tr><td>Load Balancer ADC<\/td><td>111560<\/td><td><code>BNADC-16586<\/code><\/td><td>Web Security Gateway<\/td><td>111560<\/td><td><code>BNYF-24789<\/code><\/td><\/tr><tr><td>Message Archiver<\/td><td>111560<\/td><td><code>BNMA-32468<\/code><\/td><td colspan=\"3\">Version thresholds given for ESG only <strong>[Unknown]<\/strong> fixed firmware for the others<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Source: <a href=\"https:\/\/trust.barracuda.com\/security\/pre-authentication-authorization-bypass-command-injection\" target=\"_blank\" rel=\"noopener\">Barracuda advisory<\/a>.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>[Confirmed]<\/strong> On 5 November Barracuda changed CVE-2026-116606&#8217;s &#8220;Authentication Required&#8221; field to &#8220;No (Administrative UI Access Required)&#8221;: no credentials, but the admin UI must be reachable. (<a href=\"https:\/\/trust.barracuda.com\/security\/pre-authentication-authorization-bypass-command-injection\" target=\"_blank\" rel=\"noopener\">Barracuda<\/a>) KEV says the bypass lets an attacker invoke config-import and restore a crafted backup, and the injection runs root commands &#8220;when the crafted timezone value is subsequently processed&#8221;. (<a href=\"https:\/\/raw.githubusercontent.com\/cisagov\/kev-data\/develop\/known_exploited_vulnerabilities.json\" target=\"_blank\" rel=\"noopener\">CISA KEV<\/a>) <strong>[MAG212 analysis]<\/strong> That points to a crafted backup that sets a malicious timezone value. <strong>[Unknown]<\/strong> Tooling, actors, start date and the Mandiant pages&#8217; contents.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What to look for<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>[MAG212 analysis]<\/strong> With no published IOCs: config-import or backup-restore events you didn&#8217;t start, unexpected timezone changes, and admin-UI connections from outside your management networks.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Investigate, contain and remediate (in order)<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Restrict the admin UI now<\/strong> to trusted networks; this is Barracuda&#8217;s workaround. (<a href=\"https:\/\/trust.barracuda.com\/security\/pre-authentication-authorization-bypass-command-injection\" target=\"_blank\" rel=\"noopener\">Barracuda<\/a>)<\/li>\n\n\n<li><strong>Confirm the latest firmware and the patch ID<\/strong> on every device. Devices several versions behind may need more than one update; apply manually if auto-patching didn&#8217;t run. (<a href=\"https:\/\/documentation.campus.barracuda.com\/wiki\/x\/n4BGOQ\" target=\"_blank\" rel=\"noopener\">Barracuda Campus<\/a>)<\/li>\n\n\n<li><strong>Triage before you trust a patched box.<\/strong> <strong>[MAG212 analysis]<\/strong> Treat any appliance with an internet-reachable admin UI since 2 November as possibly compromised: preserve logs, review config history, involve Barracuda support or your IR provider.<\/li>\n\n\n<li><strong>[MAG212 analysis]<\/strong> If compromise is suspected, rotate LDAP bind, SMTP relay and admin credentials, and consider rebuilding rather than cleaning.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Verify recovery:<\/strong> the patch ID shows as applied on every device; the admin UI doesn&#8217;t answer from an external vantage point; config history re-reviewed after patching. <strong>Lesson<\/strong> <strong>[MAG212 analysis]<\/strong>: MSPs should inventory admin-UI exposure across every client appliance this week.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why it matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Email and web gateways sit on the boundary, hold relay and directory credentials, and see every message an organisation sends and receives. Barracuda ESG has been a target for state actors before, and appliances in small businesses, schools and MSP client estates are often patched automatically but rarely inspected. A patched box that was opened before the patch landed is still a compromised box.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The bottom line<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Restrict every Barracuda admin interface to trusted networks today, confirm the patch ID on each device rather than trusting auto-update, and treat any appliance whose admin UI was reachable since 2 November as a forensic case until its configuration history says otherwise.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>How we label evidence: <strong>[Confirmed]<\/strong> comes from a primary source such as a vendor or CISA; <strong>[Reported]<\/strong> from a secondary outlet; <strong>[Claimed]<\/strong> from an attacker or an unverified party; <strong>[MAG212 analysis]<\/strong> is our judgement; <strong>[Unknown]<\/strong> means not established at press time. Commands and indicators are copied from the cited sources and were not tested by MAG212 CYBER.<\/em><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">This story is part of <a href=\"https:\/\/cyber.mag212.com\/mag212-cyber-daily-2026-11-11-barracuda-outlook-xen-orchestra-fortinet\/\">MAG212 CYBER Daily, 11 November 2026<\/a>, with the day\u2019s other verified stories, the Defender\u2019s Action Desk and a full source register. Get the daily briefing free: <a href=\"https:\/\/cyber.mag212.com\/subscribe-free\/\">subscribe to MAG212 CYBER<\/a>. By El Mostafa Ouchen.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Barracuda confirms exploitation of CVE-2026-116606 and CVE-2026-111560, which chain to root on Email Security Gateway and five other appliance lines. CISA wants fixes and forensic triage by 13 November. Affected products, patch IDs, what to look for and the order of response.<\/p>","protected":false},"author":1,"featured_media":4156,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,15,14],"tags":[197,62,299,30],"class_list":["post-4158","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-critical-cves","category-threat-intelligence","category-vulnerabilities","tag-barracuda","tag-cisa-kev","tag-email-security","tag-zero-day-vulnerabilities"],"_links":{"self":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/comments?post=4158"}],"version-history":[{"count":1,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4158\/revisions"}],"predecessor-version":[{"id":4181,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4158\/revisions\/4181"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media\/4156"}],"wp:attachment":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media?parent=4158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/categories?post=4158"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/tags?post=4158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}