Contact us
← Article questionsDoes this affect us?

CVEHit Business Advisory by IntegrityLab.ai

Does this affect us?

Confirm the Email Security Gateway fix. The sources disagree about firmware 9.4.0.029. — CVE-2026-116606: Business Triage

Check these three things.

Start by confirming the installed fix with Barracuda.

  1. System owner: confirm the latest firmware and the applicable security patch with Barracuda. The sources disagree about firmware 9.4.0.029.
    What to confirm
    • This check is for Barracuda Email Security Gateway only.
    • Do not apply CVE-2026-116606 to other Barracuda products.
    • Installed firmware version.
    • Security patch recorded on the appliance, if any.
    • Source of each record.
    • Date checked.
    SourceFirmware and patch guidance
    Barracuda trust advisory, retrieved November 11, 2026:
    • Email Security Gateway is affected by CVE-2026-116606.
    • Run the latest firmware and all security patches.
    • Remediation line: upgrade to the latest firmware version.
    Barracuda trust advisory, retrieved November 11, 2026:Patch BNSF-40425 (9.4.017+).
    Barracuda trust advisory, retrieved November 11, 2026:Patch BNSF-40430 (<9.4.017).
    Barracuda campus page, retrieved November 11, 2026:
    • All Email Security Gateway versions are affected.
    • Firmware 9.4.0.029 includes the patches.
    • Upgrade to 9.4.0.029 and above.
    • Firmware 9.4.0.029 or later confirms the update.
    • A firmware update was released for 9.1 through 9.4.0.027.
    CVE record published by Mandiant on November 2, 2026:
    • Versions earlier than 9.4.0.030 are affected.
    • Default status is unaffected. That default does not clear versions earlier than 9.4.0.030.
    • Keep each source's notation. These pages do not say that 9.4.017 and 9.4.0.029 are the same number.
    • Ask Barracuda which statement fits this appliance. Do not choose 9.4.0.029 or 9.4.0.030 from these pages alone.
    • If the installed fix is not confirmed, treat the appliance as possibly affected. That is not proof it is vulnerable.
    • An older firmware number is not proof of vulnerability when the applied patch is unknown.
    • These sources do not describe a backport.
    • A confirmed fix still leaves earlier exposure for the log review.
  2. Network owner: confirm whether the administrative user interface is reachable from outside trusted networks. No login is required.
    When the risk applies
    • The attacker must be able to reach the administrative user interface.
    • No login and no administrator account are required.
    • Barracuda's November 5, 2026, 2:30pm EST update says authentication is not required.
    • That update set the field to No (Administrative UI Access Required).
    • That phrase means the interface is reachable. It does not mean the attacker already has an administrator login.
    • Barracuda says an interface that is not reachable from the internet is less exposed.
    • Barracuda recommends limiting the interface to trusted internal networks.
    • Less exposure is not a completed patch.
    • The fix can be required even when the interface is already restricted.
    • Appliance checked.
    • Whether untrusted networks can reach the admin interface.
    • Source of the record.
    • Date checked.
    • A public website response does not establish this interface.
  3. Security owner: review existing logs for unauthorized changes. Include mail-flow problems.
    What the records can show
    • Preserve the records before updating the appliance.
    • Barracuda's securing guide, dated September 17, 2026, says syslog records:
      • User login activity.
      • Configuration changes.
      • Mail-flow data, the same information as the Message Log.
    • Include existing records of access to the administrative interface if you already keep them.
    • Unexpected configuration changes.
    • Unexpected logins.
    • Unexpected mail-flow changes.
    • Mail-flow interruption.
    • These are the product's own logs. Barracuda does not publish a separate indicator list in these sources.
    • Include appliances that were reachable before the fix was confirmed, including appliances updated since.
    • If the records show an unexpected configuration change or unauthorized access, Security owner starts response now.
    • Act on that evidence even if this CVE is not established as the cause.
    • A completed patch does not show whether an earlier change happened.
    • A clean log does not prove the configuration was unchanged.
    • A missing log leaves the harm question unresolved.
    • Barracuda's report of a small number of organizations does not show that this appliance was changed.
    • The KEV listing does not show that this organization was attacked.
    • The KEV listing does not count the attacks.

If the records show an unexpected configuration change or unauthorized access, Security owner starts response now. Act even if this CVE is not established as the cause. Barracuda's November 9, 2026 report of a small number of organizations is not evidence about your appliance.

← Back to article questions

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…