Skip to content
← All insights

Cybersecurity4 min read

Barracuda Email Security Gateway: Who Could Reach the Admin Page?

After confirmed Barracuda exploitation, verify your gateway patches, reconstruct admin access and confirm mail still flows.

A white envelope and a rack appliance sit behind a dark mesh partition.
Conceptual illustration of separation between mail delivery and gateway administration.

A security alert about your email gateway usually sends IT straight to the firmware screen. There is another screen worth opening first: the firewall rule that decides who can reach the gateway’s administration page. If an attacker could reach that page while the device was vulnerable, a successful update today leaves a question about yesterday.

What Barracuda and MyCERT confirmed

Barracuda published its advisory on 2 November 2026. In an update dated 9 November in the vendor’s time zone, it confirmed that it had observed exploitation affecting a small number of organisations. On 10 November, the US Cybersecurity and Infrastructure Security Agency added both vulnerabilities to its Known Exploited Vulnerabilities catalogue, as recorded by the Canadian Centre for Cyber Security. Malaysia’s MyCERT also issued an advisory on the chain. These notices confirm exploitation in the wild; they do not establish that a particular Malaysian business was affected.

The distinction between the two flaws matters. CVE-2026-116606 affects Barracuda Email Security Gateway (ESG) and can bypass authorisation before sign-in if an attacker can reach the administrative interface. CVE-2026-111560 is a command injection flaw that affects ESG and several other Barracuda products. On affected ESG systems, the two flaws can be chained to gain root access, meaning control at the operating system’s highest privilege level. The first flaw is specific to ESG. Use the vendor’s product table to assess other Barracuda equipment separately.

Find out who could reach the admin page

Ask your IT team or service provider to list each ESG instance, its firmware and patch status, and the network paths to its administrative interface. Put production and standby appliances on the same list. Check firewall and cloud rules, port forwards, approved vendor access and VPN routes. Then verify the intended restrictions from an authorised test location. A diagram or a rule description tells you what someone planned; a reachability test gives you evidence of what is possible today.

Ask a second question: what was reachable before the update? Compare the patch installation time with firewall change records, configuration backups and available logs. A temporary rule may have closed before anyone saw the advisory. If records are incomplete, write down the dates you could verify and mark the rest as unknown. And keep the public mail route separate in the change plan: restricting the administrative interface should not require shutting down normal mail delivery.

Fix the device and investigate earlier exposure

Restrict administration to trusted management networks and approved access paths, following Barracuda’s guidance. Apply the vendor’s supported firmware and applicable patches, and obtain evidence from each device that they took effect, including any standby node. Barracuda notes that older firmware may need more than one update. Its advisory also lists patch identifiers for different ESG builds, so ask Barracuda Support to confirm coverage if your provider cannot verify the installed patch against the appliance’s branch.

If an affected administrative interface was exposed or you cannot establish its history, involve your security team and Barracuda Support promptly. Preserve available evidence such as firewall logs and relevant appliance records, and agree with responders on containment and collection before wiping or rebuilding. Ask them to use current vendor and MyCERT guidance to decide what to examine, what access or credentials may need review, and whether recovery from a known clean state is warranted. An empty search means less when logs cover only part of the exposure window.

What an owner should ask to see

Hypothetical example: A distributor in Selangor runs a primary gateway and a standby appliance. IT checks both after the advisory and finds that only the standby had an internet-facing management rule left over from a support session. The team removes that rule, records the patch state of both devices, saves firewall logs and opens a vendor case to assess the standby. The operations lead separately verifies inbound and outbound mail, including a test message to a branch. That leaves the owner with two clear facts: mail is working, and the earlier exposure has its own investigation owner.

Close the patch ticket when you have evidence of the fix and the restricted access path. Track any unanswered incident question separately, with a named owner and the date of the next decision. If your business needs a second pair of eyes on a gateway’s exposure or on the handover between IT and incident response, talk to AXO Technologies.

Sources and dates

← Explore all insightsDiscuss your priorities with AXO ↗