Barracuda ESG Chain CVE-2026-116606 and CVE-2026-111560 Now Exploited: No Login to Root on Email Gateways, CISA Sets a Three-Day Deadline

Cyber · 2026-11-11 · By H.A

Barracuda ESG Chain CVE-2026-116606 and CVE-2026-111560 Now Exploited: No Login to Root on Email Gateways, CISA Sets a Three-Day Deadline

Barracuda now says attackers have exploited its patched Email Security Gateway authorization-bypass and command-injection chain against a small number of organisations, and CISA has given federal agencies until 13 November to fix it.

Barracuda has confirmed that attackers are now exploiting the two Email Security Gateway (ESG) flaws it patched at the start of November. Chained together, CVE-2026-116606 and CVE-2026-111560 take an attacker from no login to root on the appliance. CISA added both to its Known Exploited Vulnerabilities (KEV) catalog on 10 November 2026 and gave US federal civilian agencies until 13 November to fix them, an unusually short three-day window.

What Is New

When Barracuda released the fixes on 2 November, there was no known exploitation, no KEV listing and no public exploit code. Researchers had published only a detection tool that checks whether an appliance is vulnerable.

That changed with a Barracuda advisory update posted on the evening of 9 November (10 November UTC). The update says the chain has been exploited against "a small number of organizations". CISA followed within hours. One report claims exploitation began after a public proof-of-concept appeared. Other sources have not confirmed this, and Barracuda has not said how attackers built their exploit.

Barracuda has not disclosed how many organisations were hit, what the attackers did after gaining access, or any indicators of compromise. No threat actor has been publicly linked to the activity.

Technical Details

CVE-2026-116606 is an authorization bypass in ESG, rated 9.3 under CVSS v4.0. In a 5 November correction, Barracuda clarified that it needs no authentication, but the attacker must be able to reach the appliance's administrative interface.

CVE-2026-111560 is an OS command injection tied to the timezone setting, rated 8.6. On its own it requires administrative access. Combined with the authorization bypass, that requirement disappears.

Together, the two flaws let an unauthenticated attacker who can reach the admin UI run commands as root and take full control of the gateway.

Who Is Affected

Email gateways sit in the path of all inbound and outbound mail. An attacker with root on one can read, copy or tamper with messages, harvest credentials and use the device as a trusted foothold inside the network. Barracuda ESG has been targeted before: in 2023 a state-backed group exploited a different ESG zero-day so deeply that the vendor told customers to replace affected appliances. No link between that campaign and the current activity has been established.

Patch Status

Barracuda released patches on 2 November 2026. Its advisory lists the ESG fixes as:

Some reports instead cite a fixed firmware number, so check the patch level against Barracuda's own advisory table rather than a single version string. The other five product lines have their own product-specific patches, listed in the same advisory.

What To Do Now

  1. Verify, don't assume. Confirm the correct patch is installed on every ESG, including standby or high-availability nodes and appliances at remote sites. Don't rely on automatic updates alone.
  2. Lock down the admin interface. It should only be reachable from a trusted management network. Review firewall rules, NAT and remote-access exceptions that may expose it to the internet.
  3. Patch the other product lines (ADC, Message Archiver, WAF, WAF Control Center, Web Security Gateway) for CVE-2026-111560, and rotate admin passwords on them.
  4. Triage for compromise. If the admin UI was ever exposed, or you see unexplained configuration changes (especially to timezone or system settings), new admin accounts or unusual outbound connections from the gateway, preserve logs and configuration and start incident response. CISA's KEV entries for both flaws call for forensic triage, not just patching.
  5. Check mail flow and rules after recovery for unexpected forwarding, journaling or relay settings that could silently copy mail.

Why It Matters

This is the familiar pattern of a patched edge-device bug turning into an exploited one within about a week. CISA's three-day deadline shows how seriously the agency takes this chain. Email security appliances are trusted, internet-facing and see sensitive data, which makes them an ideal target.

Organisations that marked these CVEs as "patch in the next cycle" when they were disclosed should move them to the top of the queue. Patching after a compromise does not remove an attacker who is already on the box, so anyone who was exposed should also check for compromise.

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Passive OSINT lookups for the recon phase of an engagement, plus offline hash identification and a payload cheatsheet.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.