Check these three things.
Start by confirming the installed fix with Barracuda.
-
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.
Source Firmware 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.
-
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.
-
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.
Do Now
- System owner: install the latest firmware and the applicable security patch.
Proof the update is done
- Confirm the installed build with Barracuda.
- Do not treat 9.4.0.029 as settled.
- If Barracuda has already confirmed the fix, record that evidence. A version number alone is not that confirmation.
- Show Barracuda the conflict.
- Do not invent a backport.
- If the firmware is multiple versions out of date, Barracuda says more than one update may be needed. Contact Barracuda Support.
- This action is for Email Security Gateway.
- Installed firmware after the work.
- Patch Barracuda confirmed.
- Source of the record.
- Date checked.
- Network owner: restrict the administrative user interface to trusted networks. This does not prove the patch is installed.
What to record
- Limit the interface to trusted internal networks.
- Barracuda recommends network access controls for that interface.
- No login is required for this flaw. Reachability is the condition.
- If access is already limited, record that evidence.
- The appliance can need the fix even when the interface is already restricted.
- Appliance.
- Who can reach the interface.
- Source of the record.
- Date checked.
- Security owner: preserve login and configuration records before any update.
Where to look first
- Review the preserved records for unauthorized changes.
- Syslog user logins.
- Syslog configuration changes.
- Existing admin-interface access records, if you already keep them.
- Start with appliances that were reachable before the fix, including appliances updated since.
- If a change or unauthorized access is present, start response now.
- Act even if this CVE is not established as the cause.
- A later patch does not settle earlier changes.
- A clean log is not proof of no change.
- A missing log leaves the question unresolved.
- Records reviewed.
- Source of the records.
- Period covered.
- Date reviewed.
- Operations owner: review mail-flow records and existing service alerts for unexpected changes or interruption.
When to escalate
- Syslog mail-flow data.
- The Message Log.
- Existing service alerts for mail interruption.
- If customer or staff mail is interrupted or unexpectedly changed, handle it as a service incident now.
- Handle that interruption even when this flaw is not yet shown to be the cause.
- Send signs of unauthorized access to the Security owner.
- A mail problem by itself does not prove this CVE.
- Records reviewed.
- Source of the records.
- Date reviewed.
Do Next
- System owner: if automatic patching is off, turn it on after Barracuda confirms the right patch.
What to record
- Barracuda recommends automatic patching when customers have turned it off.
- Turn it on after Barracuda confirms the patch for this firmware.
- Automatic patching does not replace that confirmation.
- Whether automatic patching is on.
- Source of the record.
- Date checked.
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
The reported finding
Authentication bypass can change the appliance global configuration
CVE record →- Required conditions
- The product in the CVE record is Barracuda Email Security Gateway.
- The CVE record says versions earlier than 9.4.0.030 are affected.
- The attacker can reach the administrative user interface.
- No login and no administrator account are required.
- The CVE record says the attacker restores a crafted, compatible backup archive.
- These sources include no reproduction steps.
- Reported outcome
- Unauthorized modification of the appliance's global configuration.
- The CVE record calls this an authentication bypass that uses an alternate path. The weakness name is CWE-288.
- This CVE alone is not described as remote code execution.
- Barracuda identifies CVE-2026-111560 as a separate command-injection flaw.
- Barracuda says the two flaws together could bypass authorization controls and give root access to the device.
- The KEV short description says this vulnerability can be chained with CVE-2026-111560. That sentence does not itself say root access.
- Ratings
- Mandiant, in the CVE record: CVSS 4.0 base score 9.3, severity Critical.
- Mandiant vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N.
- That vector rates the appliance impact high and the subsequent-system impact none.
- That vector leaves exploit maturity Not Defined. That field is not a statement of no exploitation.
- Barracuda trust advisory: severity High, score 9.3.
- The number matches. The severity word does not. Keep Critical with Mandiant and High with Barracuda.
- Known exploitation
- CISA coordinator entry in the CVE record, SSVC timestamp November 2, 2026, version 2.0.3:
- Exploitation: active.
- Automatable: yes.
- Technical Impact: total. That is CISA's label for the vulnerability. It is not a finding that your organization was compromised.
- The CISA assessment source is the CVE record on CVE.org. These sources do not include a separate CISA.gov per-CVE assessment.
- The CVE record's November 11, 2026 update is the CISA enrichment. The Mandiant description date is November 2, 2026.
- Official KEV catalog JSON, version 2026.11.10, released November 10, 2026, includes this CVE.
- Date added: November 10, 2026.
- Due date: November 13, 2026. That is the catalog's federal date. It is not a deadline for every company.
- Forensic triage: Yes. For this advisory, the supported review is the log review above.
- Known ransomware campaign use: Unknown. The entry does not establish ransomware use.
- The KEV required action points federal stakeholders to vendor instructions, CISA directive BOD 26-04, and CISA forensic triage requirements.
- Barracuda, November 9, 2026, at 9:00pm EST: observed exploitation affecting a small number of organizations.
- That note does not name the organizations and does not give a count beyond a small number.
- The trust page's CVE block says published November 2, 2026 and updated November 2, 2026. The same page also carries the November 5 and November 9 notes above.
- CISA coordinator entry in the CVE record, SSVC timestamp November 2, 2026, version 2.0.3:
Fix guidance
- Barracuda's confirmed direction is the latest firmware and the applicable security patches.
- The version line is unresolved. Confirm the installed firmware and patch with Barracuda. Do not invent a backport.
- Confirming the fix today does not show whether the interface was reachable earlier.
- Confirming the fix today does not show whether the configuration was changed earlier.
What IntegrityLab.ai can check
- The authorized unauthenticated web check can record:
- A reachable web service.
- The server identification returned in the response.
- That response is a clue for an administrator.
- It does not establish:
- Installed product.
- Firmware.
- Security patch.
- Vulnerable configuration.
- Compromise.
- No identifying response does not rule Email Security Gateway out.
- A front server can hide the appliance behind it.
- This bounded review did not run a scan.
- This review did not establish a validated detection check for CVE-2026-116606.
- The check cannot confirm that an administrative interface is exposed.
- The check cannot confirm Barracuda patch status.
- A general website assessment does not reach an internal administrative interface.
- A general website assessment does not establish a provider's inventory.
- The System owner must establish those facts from internal records.
- Provider must establish those facts when Provider holds the appliance records.
Sources and vendor guidance
- CVE record, including the Mandiant description and the CISA assessment (retrieved November 11, 2026)
- Barracuda trust advisory (retrieved November 11, 2026)
- Barracuda campus firmware note (retrieved November 11, 2026)
- Barracuda guide to securing Email Security Gateway (retrieved November 11, 2026)
- Official KEV catalog JSON, version 2026.11.10, containing this CVE (retrieved November 11, 2026)
- Readable KEV catalog page filtered to this CVE