Skip to main content
All incident reports
Incident report

Barracuda breach: an unretired vendor key, an AI attack framework, and two exploited appliance flaws

Barracuda Networks has had two separate security problems in the first half of November: a breach of its own cloud environment, and a pair of appliance flaws that attackers are now exploiting at customer sites. No public source links the two. This report keeps them apart and sets out what is confirmed about each.

· First published

The short version

  • The breach. An attacker used a valid cloud access key to get into about 10 of Barracuda's cloud accounts over roughly 44 hours on 1 and 2 November. Barracuda found the intrusion on 4 November.
  • How they got in. The key had been issued to a third-party vendor for a past project and was never retired. Barracuda says the attacker took it in October from a configuration file in that vendor's GitHub repository.
  • The tooling. Barracuda says the intrusion matches Artex, an open-source AI penetration-testing framework that the FBI has warned is being used in real attacks.
  • Customer impact. The attacker reached a system holding customer integration credentials for Barracuda XDR. Barracuda found no evidence they were taken, and has asked potentially affected customers to replace them.
  • The appliance flaws. Separately, CVE-2026-116606 and CVE-2026-111560 in Barracuda's Email Security Gateway can be chained to reach root without a login. Both are being exploited and both are in CISA's Known Exploited Vulnerabilities catalogue.

Timeline

DateEvent
OctoberAttacker obtains a Barracuda cloud access key from a third-party AI vendor's GitHub repository, according to Barracuda
1–2 NovAttacker works through about 10 Barracuda cloud accounts in roughly 44 hours
2 NovBarracuda releases patches for CVE-2026-116606 and CVE-2026-111560
4 NovBarracuda discovers the cloud intrusion
5 NovwatchTowr publishes the full attack chain for the two appliance flaws
9 NovBarracuda updates its advisory: the flaws are being exploited against a small number of organisations
10 NovCISA adds both flaws to its Known Exploited Vulnerabilities catalogue
9–11 NovPrevidian records 17 exploitation attempts against CVE-2026-116606 from 15 IP addresses in three countries
16 NovBarracuda's account of the cloud breach is reported

The cloud breach

Barracuda's own account is direct about the cause. The access key was given to a vendor, described only as a company working in AI, for the length of a project. "We did not retire the key when the vendor — a company working in AI — finished that work. That is on us," the company said.

From that one key the attacker moved outward by reusing whatever credentials each system gave up. Barracuda says the intruder reached its data analytics environment, source-code repositories and Kubernetes clusters, and went looking through secret stores, configuration, service accounts and server metadata services. On some servers the attacker had shell access and searched for cryptocurrency wallet material: Ethereum keystore files, seed phrases and private keys.

The attacker tried to stay. A container was deployed that mounted the host's file system, and a backdoor was left in a Kubernetes cluster. A separate attempt to create a new cloud administrator identity was blocked.

Barracuda believes the motive was financial, based on the wallet hunting, but does not rule out that this was cover for something else. It has not attributed the attack to any group.

Why Artex matters here

Artex was published on GitHub in July 2026 as a security-testing tool: a planner sets an objective, agents carry out the tasks, and the platform records what they find. Its developer removed the repository in October, but it continues to circulate. In early November Censys counted roughly 1,500 hosts running exposed Artex consoles.

An FBI alert says the framework lets operators with little technical skill run complex operations against many targets at once. SentinelOne, Cisco Talos and Amazon have each described campaigns that used it, by state-linked and financially motivated groups alike. Barracuda says the probe names, the order of the attacker's work and the built-in routines for hunting credentials and wallets all match Artex, and that the intrusion resembles the one at hosting platform Railway in October.

Amazon's finding is the one to hold on to: the agents used long-known techniques, and succeeded where basics were missing, such as hardcoded credentials, keys left in code and unauthenticated interfaces. The speed is new. The way in is not.

The appliance flaws

CVE-2026-116606 (CVSS 9.3) is an authentication bypass in the Email Security Gateway. CVE-2026-111560 (CVSS 8.6) is a command injection that runs as root and normally needs an administrator account. On the Email Security Gateway the first supplies the access the second needs, so the pair gives root with no login. The command injection also affects Load Balancer ADC, Message Archiver, WAF Control Center, Web Application Firewall and Web Security Gateway, where it still requires an administrator account.

Exploitation needs access to the appliance's administrative interface. Barracuda and CISA have not described the attacks beyond saying a small number of organisations were affected.

What is not known yet

  • Who carried out the cloud breach.
  • Which vendor's repository held the key.
  • Whether any customer data or integration credentials were actually taken. Barracuda says it found no evidence of it.
  • Who is exploiting the appliance flaws, and how many organisations have been hit.
  • Whether there is any connection between the two events. Nothing published says there is.

What to do

If you use Barracuda Managed XDR Cloud or Monitored Endpoint

  1. Revoke and recreate your integration credentials if Barracuda has contacted you. Barracuda says customers who were not contacted need take no action.

If you run Barracuda appliances

  1. Apply the patch for each affected product. The Email Security Gateway is fixed in firmware 9.4.0.030 and later.
  2. Confirm the administrative interface is reachable only from trusted internal networks, not from the internet.
  3. Turn automatic patching back on if it was switched off.
  4. Because exploitation began before many organisations patched, check appliances for signs of compromise, not only for the patch level.

For everyone else, the lesson travels

  1. List every access key and token issued to a vendor, contractor or integration, and retire the ones whose project has ended.
  2. Give vendor credentials an expiry date when they are issued.
  3. Search public code repositories, your own and your suppliers', for your organisation's keys and secrets.
  4. Treat any credential found in one system as a route into the next, and scope it accordingly.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.