Contact us
← CVEHit Business AdvisoryBarracuda appliance flaw gives administrators root control — CVE-2026-111560: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published

Barracuda appliance flaw gives administrators root control — CVE-2026-111560: Business Triage8.6/10High · CVSS 4.0Mandiant (CVE record)Fix availablePatch per productCISA assessmentCVE.org sourceKEV listingAdded Nov 10, 2026

Patch affected Barracuda appliances and keep their administrative interfaces off untrusted networks. Research: primary sources retrieved 2026-11-11 to 2026-11-16.

Check these three things.

  1. System owner: confirm each affected Barracuda appliance has its security patch applied, such as BNSF-40425 on Email Security Gateway 9.4.017 or later.
    What to confirm
    • Affected products, from the Barracuda advisory:
      • Email Security Gateway.
      • Load Balancer Application Delivery Controller.
      • Web Application Firewall.
      • Web Security Gateway.
      • Message Archiver.
      • WAF Control Center.
    • Patch for each product, from the Barracuda advisory:
      • Email Security Gateway 9.4.017 or later: BNSF-40425.
      • Email Security Gateway below 9.4.017: BNSF-40430.
      • Load Balancer Application Delivery Controller: BNADC-16586.
      • Web Application Firewall: BNADC-16586.
      • Web Security Gateway: BNYF-24789.
      • Message Archiver: BNMA-32468.
      • WAF Control Center: BNWF-60060.
    • Affected through these versions, as written in the CVE record:
      • Email Security Gateway: 9.4.0.27.
      • Load Balancer Application Delivery Controller: 6.4.0.
      • Web Application Firewall: 11.0.1.
      • Web Security Gateway: 16.1.100.100.
      • Message Archiver: 5.5.4.0.
      • WAF Control Center: 2.2.1.
    • Limits on the fix information:
      • The retrieved Barracuda page names patches, not fixed version numbers.
      • The CVE record writes the Email Security Gateway limit as 9.4.0.27. Barracuda writes 9.4.017. The sources do not reconcile the two formats, so confirm the patch on the device.
      • Barracuda says the device shows the latest firmware version available. A device several versions behind may need more than one update.
  2. Network owner: confirm the administrative interface of each affected Barracuda appliance is reachable only from trusted internal networks.
    When the risk applies
    • Conditions from the sources:
      • The attacker must be an authenticated administrator of the appliance (CVE record, Barracuda advisory).
      • Barracuda says exploitation requires access to the administrative interface.
      • Barracuda says organizations whose administrative interfaces are not publicly reachable are less exposed.
    • Open item: whether a reachable sign-in page is the administrative interface of an affected appliance. The sources do not say. Firewall rules and the appliance access settings answer it.
    • Email Security Gateway only: the same Barracuda advisory lists a separate flaw, CVE-2026-116606, a pre-authentication authorization bypass. Barracuda says the two flaws together could let an attacker bypass authorization and obtain root access. That flaw also requires access to the administrative interface.
    • Records to check:
      • Firewall rules that allow access to each appliance's administrative interface.
      • The appliance's own administrative access settings.
      • The source and date of each record.
  3. Security owner: review appliance administrator sign-in and configuration records for changes nobody authorized, including the timezone setting.
    What the records can show
    • Why this check matters now:
      • Barracuda reports exploitation activity affecting a small number of organizations.
      • CISA added the flaw to KEV on 2026-11-10.
    • Records to review:
      • Administrator sign-in history.
      • Configuration change history.
      • The current timezone value, because the reported weakness is a crafted timezone value.
      • The source and date of each record.
    • Limits:
      • The retrieved sources name no specific signs of compromise, so this review cannot rule harm out.
      • A patch does not rule out earlier harm.
      • If the records show unauthorized administrator activity, start incident response.

Act first on unpatched appliances with a reachable administrative interface. Patch them, then review earlier administrator activity.

Do Now

  • System owner: update each affected Barracuda appliance with its listed patch, such as BNSF-40425 on Email Security Gateway 9.4.017 or later.
    What to ask
    • Completion evidence:
      • The appliance runs the latest firmware version.
      • The appliance record shows its required security patch and all other security patches applied.
      • The date of the update.
    • Barracuda says to apply the patch manually if it was not applied automatically.
    • Barracuda Campus has the manual patch and firmware steps.
    • Barracuda Support can help with firmware versions or patches: support@barracuda.com.
  • Network owner: restrict the administrative interface of each affected Barracuda appliance to trusted internal networks.
    What to ask
    • Barracuda recommends trusted internal networks and network access controls for administrative interfaces.
    • Completion evidence:
      • The firewall rule or appliance setting that limits access.
      • The date of the change.
  • Security owner: start incident response if appliance records show unauthorized administrator activity or an unexpected timezone value.
    What to ask
    • Reason: exploitation is reported, and a patch does not undo earlier harm.
    • Completion evidence:
      • The review result.
      • The records reviewed, with their sources and dates.

Do Next

  • System owner: set each appliance to receive patches automatically where automatic patching is off.
    What to ask
    • Barracuda recommends this setting for customers who turned off automatic patching.
    • Completion evidence: the appliance setting and the date it was changed.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

The reported finding

OS command injection in the timezone setting (CWE-78)

Original advisory →
Required conditions
An authenticated administrator of an affected Barracuda appliance supplies a crafted timezone value, and the appliance later processes it. Barracuda says exploitation requires access to the administrative interface.
Reported outcome
Operating system commands run with root privileges. In plain words, the appliance fails to neutralize shell metacharacters, which are special characters the operating system reads as instructions. The CVE record scores it CVSS 4.0 8.6 (Mandiant). GitHub lists CVSS 3.1 7.2. The sources name no other systems as affected.

Fix guidance

  • Barracuda lists a patch for each affected product and says to upgrade to the latest firmware.
  • The CVE record gives affected versions through 9.4.0.27, 6.4.0, 11.0.1, 16.1.100.100, 5.5.4.0 and 2.2.1 for the six products in the order listed in the first check. Barracuda's page names patches, not fixed version numbers.
  • Exploitation status: Barracuda updated its advisory on November 9, 2026 to report exploitation activity affecting a small number of organizations. The CISA ADP record lists exploitation as active (SSVC, 2026-11-02), automatable as no and technical impact as total. CISA added the flaw to KEV on 2026-11-10. A patch does not rule out earlier harm.

What IntegrityLab.ai can check

  • Current assessor source inspection, verified 2026-11-16, shows that web-service discovery keeps the URL, host, port, response status, page title, web-server banner and technology indications.
  • An exact search of the current assessor source found no match for Barracuda or CVE-2026-111560. This review does not establish a validated detector for this CVE. It does not establish absence from a deployed service or from dynamically downloaded templates.
  • A reachable web service does not establish the affected product, installed version, user permissions, vulnerability or compromise. This review involved no scan and no detector execution.

How to read the score

Mandiant (CVE record) CVSS 4.0: 8.6 (High). CVSS 3.1: 7.2 (GitHub): High. Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

Need an independent review of your public exposure?

See IntegrityLab.ai →

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…