Cyber & AI intelligence
Wasteland.
Briefs indexed3683
Issues36
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-116606 2026-11-10

Barracuda ESG Authentication Bypass (CVE-2026-116606) Added to CISA KEV

"CISA has confirmed active exploitation of CVE-2026-116606, an authentication bypass in Barracuda Email Security Gateway. The flaw lets an unauthenticated remote attacker change the appliance's global configuration…"

CISA has confirmed active exploitation of CVE-2026-116606, an authentication bypass in Barracuda Email Security Gateway. The flaw lets an unauthenticated remote attacker change the appliance's global configuration. Federal remediation is due by November 13, 2026.

What Is It

CVE-2026-116606 is an authentication bypass in Barracuda Networks Email Security Gateway (ESG). It works through an alternate path or channel (CWE-288). An unauthenticated remote attacker can call a configuration-import function and restore a crafted backup archive that the appliance accepts as compatible. This lets them change the appliance's global configuration without authorization. CISA notes that this flaw can be chained with CVE-2026-111560.

Mandiant reported the vulnerability (MNDT-2026-0042). It was published to NVD on November 2, 2026. NVD's analysis is still in progress.

Why It Matters

What's Vulnerable

Patch Status

NVD lists versions before 9.4.0.030 as affected. Barracuda's security advisory is linked below.

CISA's required action is to apply mitigations according to the vendor's instructions. Federal civilian executive branch (FCEB) agencies must also follow BOD 26-04 ("Prioritizing Security Updates Based on Risk") and CISA's "Forensics Triage Requirements." Binding operational directives apply only to those agencies. Other organizations are not bound by BOD 26-04, but CISA recommends they use the KEV catalog to prioritize their own fixes. For cloud services, follow the applicable BOD 26-04 guidance. If no mitigations are available, stop using the product. Stakeholders should check each asset's internet exposure and follow the BOD 26-04 patching guidelines.

Because this CVE can be chained with CVE-2026-111560, defenders should check their exposure to both.

Sources