CVEHit Business Advisory by IntegrityLab.ai
What’s the evidence?
Confirm the Email Security Gateway fix. The sources disagree about firmware 9.4.0.029. — CVE-2026-116606: Business Triage
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.
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
← Back to article questions