critical Cve 2026 102489 · AI Security

AI Agent Breached Bug-Hunting Nonprofit DIVD by Chaining Two Zammad Zero-Days

Data graphic: AI agent hacks the hunters. The attack chain from the internet through a Zammad session hijack CVE-2026-102489 to RCE, root CVE-2026-102490 and stolen volunteer data, with each flaw scored CVSS 4.0 9.4.
AK

Threat intelligence editor · Published Oct 2, 2026 · Updated Oct 14, 2026, 9:02 PM EDT

An autonomous AI agent chained Zammad flaws CVE-2026-102489 and CVE-2026-102490 to reach root at DIVD. What Zammad admins should check and patch now.

On 21 September 2026 an attacker broke into the Dutch Institute for Vulnerability Disclosure (DIVD), the volunteer-run nonprofit that spends its days warning other organisations about exposed and vulnerable systems. The way in was the organisation's own helpdesk: two zero-day flaws in Zammad, the open-source ticketing system, chained from a hijacked session to root on the server in seconds.

The attacker was an AI agent, DIVD says, and not a careful one. "This is an attack we have not seen before. Not because it's our first, but because the modus operandi indicates that this is an agentic AI-powered attack," the group wrote when it first went public. It described the intrusion as "loud and very very messy".

DIVD published the technical details on 1 October as case DIVD-2026-00015, with the two CVE ids, the affected versions and a script to check Zammad logs for signs of exploitation. Its advice to every Zammad operator is short: upgrade to Zammad 7, or take the system offline.

Update (2026-10-15): fixed versions named

DIVD's case file DIVD-2026-00014 (last modified 9 October) now says Zammad "has fixed both vulnerabilities the first in release 7.2 and the second in release 7.2.2". Zammad confirms the second fix in its own GitHub advisory GHSA-p97w-927q-8vxq, published 8 October: "Local privilege escalation to root in DEB/RPM packages (packager.io)", naming CVE-2026-102490, affected versions up to and including 7.2.1, patched in 7.2.2. Zammad says only installations from the DEB and RPM packages were affected, and that installations from source or the official container images were not. Upgrading to 7.2.0, as this article first advised, is not enough on a package install. Run Zammad 7.2.2 or later. DIVD has also published its overview of which data was compromised, updated on 9 October, and reports its own response times as 19 minutes to detect, 19 hours to respond and 9 hours to contain.

Update (2026-10-05): CISA lists both flaws as exploited

On 2 October CISA added both CVE-2026-102489 (session fixation, leading to remote code execution as the zammad user) and CVE-2026-102490 (improper privilege management, local escalation to root) to its Known Exploited Vulnerabilities (KEV) catalog. CISA's entries note that each can be chained with the other. The federal due date is 5 October 2026, and CISA lists known ransomware campaign use as "Unknown". CISA's required action is to apply mitigations per vendor instructions, and it flags forensic triage for both entries. Its notes point to Zammad's release page and community post. The original reporting below was written before the listing.

What happened

The timeline below comes from DIVD's case file and its statements to the press.

  • 21 September: the agent exploits the two Zammad flaws and gets into DIVD's infrastructure.
  • 22 September: DIVD spots the activity and blocks access to its data centre. It brings in an outside forensics team and notifies the police, the Dutch data protection authority (Autoriteit Persoonsgegevens) and the National Cyber Security Centre (NCSC).
  • 22–23 September: DIVD analyses and reproduces the exploit chain.
  • 24 September: DIVD reports both flaws to Zammad.
  • 26 September: DIVD starts scanning for exposed Zammad instances, makes a limited disclosure and notifies other victims.
  • 29 September: BleepingComputer reports the breach. DIVD has not yet named the flaw, beyond saying it was not Citrix NetScaler.
  • 1 October: full public disclosure, with the CVE ids, the case file and the log check script.

Data graphic: timeline of the DIVD breach. AI agent breaks in on 21 Sep, DIVD detects it on 22 Sep, reports to Zammad on 24 Sep, notifies victims on 26 Sep, BleepingComputer reports on 29 Sep, full disclosure on 1 Oct.

Ten days from the break-in to full disclosure. Source: DIVD case DIVD-2026-00015, The Register, BleepingComputer.

From Zammad, the agent moved on to other services and took data before segmentation stopped it. The Register reports that the stolen data belongs to DIVD's volunteer researchers: their DIVD email addresses and possibly other contact details. DIVD says the scope stayed limited "thanks to proper network segmentation and the actions of its IT and incident response team after detection", and it has published an overview of which data is and is not involved.

The two Zammad flaws

CVE-2026-102489CVE-2026-102490
What it doesSession hijack leading to remote code execution as the zammad userLets the local zammad user escalate to root
NeedsNo authentication (per The Register and SecurityWeek)A foothold on the server first
Affected6.3.0 to 6.5.4 exploitable; 7.0.0 to 7.1.3 contain the flaw but are not exploitableDIVD: 1.5.0 to 7.1.0-alpha. Zammad's advisory (8 Oct): DEB/RPM package installs of every released version through 7.2.1; Docker and source installs not affected
CVSS 4.09.4 (scored in the chained scenario)9.4 (scored in the chained scenario)

Neither flaw is enough alone. CVE-2026-102489 gets an outsider code execution as the unprivileged account Zammad runs under. CVE-2026-102490 turns that account into root. Chained, they hand an unauthenticated attacker the whole server, and the agent ran the chain in seconds.

Why DIVD thinks it was an agent

DIVD points to how the intrusion behaved, not to any signature. In its words, "the agent worked automated, deciding next steps itself at high speed", with "sloppy logic or pattern". It also "has done some pretty dumb things, like polluting its own MITM attack with password spraying", running a noisy credential attack through the same channel it was trying to intercept quietly.

The giveaway was the commentary. "The agent is so overexplaining in its comments that it makes our job in reverse engineering a lot easier," DIVD said. The scripts left behind were full of self-justifying notes explaining why each step was taken. A human operator does not usually write those.

That cuts both ways. A messy, badly configured agent still found and chained two unknown flaws in a widely deployed helpdesk and reached root on the first try. Its sloppiness made the forensics easy, but it did not stop the break-in. What stopped it from going further was network segmentation, which is an ordinary control.

It also fits a pattern TF has been tracking. In July, Sysdig documented JadePuffer, an extortion campaign that a language model ran from exploitation to data destruction. DIVD is the first case TF has covered where the agent's way in was a pair of zero-days rather than a known CVE.

Patch status: read the vendor and DIVD together

The two sides do not yet describe the fix the same way.

  • DIVD says Zammad 7 is safe from the chain it saw exploited, and tells users to upgrade to it or go offline.
  • Help Net Security reported on 1 October that "both flaws are currently without a fix".
  • Zammad posted on its community forum on 1 October. On CVE-2026-102489 it said "Zammad 7.0 and later are not affected" and that the change is included in Zammad 7.2.0, the current stable release. On CVE-2026-102490, it first said DIVD had not yet given it technical details. Later the same day, after receiving them, it said the issue "cannot be exploited remotely on its own" because an attacker would already need access, and again told users to update to 7.2.0.
  • As of 2 October, Zammad's GitHub security advisories listed no entry for either CVE. That has changed: the root-escalation advisory went up on 8 October (see the update above).
  • Later, DIVD and Zammad both named the fixes. DIVD's case file DIVD-2026-00014 (modified 9 October) says the first flaw was fixed in release 7.2 and the root escalation in release 7.2.2. Zammad's 5 October advisory describes the 7.2.0 change for CVE-2026-102489 as "an additional hardening measure", since 7.0 and later are "not affected in practice". Zammad 7.2 itself came out on 23 September, two days after the breach. For CVE-2026-102490, GHSA-p97w-927q-8vxq (8 October) gives 7.2.2 as the patched version and describes the cause: service processes started as root and ran files that the zammad account owned and could write, so an attacker with that foothold could escalate within seconds.
  • Severity differs by source. Zammad's advisory scores CVE-2026-102490 High, CVSS v4 8.5, local attack vector. NVD shows DIVD's v4.0 score of 9.4, which DIVD calculated for the chained scenario, and a 7.8 v3.1 score from NVD.
  • 7.2.1 matters too. Zammad's 7.2.1 security release (6 October) patches 27 issues, including remote code execution through a template sanitizer bypass in automation configuration and a session identifier disclosed in an authenticated configuration response. Container and source users, who are not hit by the root escalation, should still move to 7.2.2 or later.

In practice: Zammad 6.5 and older are end of support and fully exposed to the remote half of the chain. Version 7.x blocks that remote entry point. The root escalation hits DEB and RPM package installs of every released version through 7.2.1, not Docker or source installs, and 7.2.2 is the release that fixes it. Treat it as live on any packaged server where an attacker might already have a foothold.

What Zammad operators should do now

  1. Find every instance. That includes forgotten test and staging helpdesks, which are the likeliest to still run 6.x.
  2. Save your logs before you touch anything. The Dutch NCSC's advice is to secure application and network logs before patching, so that you can still investigate a compromise during the zero-day window.
  3. Run DIVD's IoC check script (cve-2026-102489_ioc_check_script_v2.sh, linked from case DIVD-2026-00015) against your Zammad logs.
  4. Upgrade to Zammad 7.2.2 or later. The root escalation affects DEB and RPM package installs through 7.2.1 and is fixed only in 7.2.2; Docker and source installs are not affected by that flaw, but 7.2.1 and 7.2.2 also carry many other security fixes. If you cannot do that today, take the instance off the internet until you can.
  5. If the script finds anything, assume root. Treat the host as fully compromised: rotate every credential the helpdesk could see (mail connectors, LDAP/SSO bindings, API tokens, integration keys) and rebuild rather than clean.
  6. Segment the helpdesk. A ticketing system faces the internet by design and holds customer data. It should not have a route to the rest of your network, and DIVD's own segmentation is why this breach stayed small.
  7. Watch for the follow-up. CISA's KEV listing (see the update above) means US federal agencies had to act by 5 October, and other operators should treat it as a patch-now signal. DIVD's case file DIVD-2026-00014 remains open.

The bigger point

DIVD runs on volunteers and has spent years warning other organisations about exposed systems. Its own write-up was titled "It was a matter of when, not if". The lesson for everyone else is not that agents are clever. This one was clumsy. The lesson is that an agent working at machine speed only needs one internet-facing application with an unknown bug, and every self-hosted helpdesk, wiki and ticketing tool is that application. Patch quickly, keep logs where an intruder cannot reach them, and assume the next agent will write fewer comments.

Sources

Keep reading

All latest →
  1. watchAI SecurityMicrosoft Shows Editing Fewer Than 10 Neurons Plants a Sleeper Backdoor in an AI Agent Model5 min
  2. elevatedAI SecurityMCPhantom: Coding Agents Keep Installing Archived MCP Servers That Will Never Be Patched6 min
  3. elevatedAI SecurityA Researcher's ARTEX Agent Escaped Its Sandbox and Breached WorkOS: What Leaked and Why It Worked7 min
  4. highAI Securityllama.cpp rpc-server Has Two Unauthenticated Flaws: A Stack Overflow Over RDMA and a One-Packet Crash4 min
  5. elevatedAI SecurityLoad/Mine: Fake Qwen2 Models on Hugging Face Turned GPU Inference Hosts Into Miners4 min
  6. elevatedAI SecurityClaude Code Before 2.1.251 Let Sandboxed Code Overwrite Files Outside the Workspace on macOS (CVE-2026-88968)3 min