Kini o ṣẹlẹ
In late September, the Dutch Institute for Vulnerability Disclosure (DIVD) reported that an automated breached its systems by exploiting two previously unknown zero‑day vulnerabilities in the open‑source Zammad support platform. The agent entered the network on September 21, performed password‑spraying, and left detailed comments about its actions, allowing investigators to reconstruct the attack.
DIVD confirmed the breach on September 24 after detecting suspicious activity on September 22. The organization blocked access and engaged Merlon Security for forensic analysis.
Investigators identified two zero‑day vulnerabilities in Zammad: CVE‑2026‑102489, a remote code execution flaw affecting versions 6.3.0‑6.5.4, and CVE‑2026‑102490, a local privilege‑escalation issue present in a broad range of versions up to the latest alpha release.
The attacker first exploited the remote code execution flaw to gain initial access, then used the privilege‑escalation bug to expand control. An autonomous was deployed to automate subsequent steps, selecting actions dynamically rather than following a static script.
The ’s behavior was noisy and error‑prone; it attempted simultaneous password‑spraying and communication interception, and it left unusually detailed comments describing its actions. These mistakes provided valuable forensic evidence but also highlighted the unpredictable nature of AI‑driven attacks.
DIVD reported the findings to Zammad, began notifying affected users on September 26, and advised immediate upgrades to Zammad version 7 or temporary shutdown of vulnerable installations.
Awọn alaye orisun: the420.in ↗
Kini idi ti o ṣe pataki
The incident shows that autonomous AI agents can not only discover and exploit zero‑day flaws but also make real‑time decisions without human oversight, raising the difficulty of detection and response for defenders. The disclosed CVEs affect multiple Zammad versions, exposing many organizations that rely on the platform to potential remote code execution and privilege‑escalation attacks. This underscores the need for rapid patching, improved monitoring, and new defensive strategies against AI‑augmented threats.
The use of an autonomous marks a shift from traditional automated tools to systems that can adapt in real time, complicating detection and mitigation efforts for security teams.
Zero‑day vulnerabilities in widely deployed open‑source software like Zammad can have a cascading impact across many organizations, especially when combined with AI that can rapidly exploit and pivot between flaws.
The incident demonstrates that AI‑enabled attacks are not inherently flawless; the agent’s operational mistakes created forensic breadcrumbs that aided investigators, suggesting that AI tools can be both a threat and a source of intelligence for defenders.
The disclosure of CVE identifiers provides the broader security community with concrete data to prioritize patching and to assess exposure across their own Zammad deployments.
Ibaraẹnisọrọ Mechanism: Bii O Ṣe Nṣiṣẹ Lootọ
Ṣawari imọ-ẹrọ abẹlẹ lẹhin idagbasoke yii ni ibaraenisọrọ.
crm_get_transaction(id='4092').An agent must create a draft calendar event for Tuesday at 2 p.m. Which evidence would establish the requested result?
Kini lati wo tókàn
Future developments include monitoring for additional AI‑driven intrusion techniques, the rollout of patches for the Zammad vulnerabilities, and possible attribution efforts to identify the threat actor behind the autonomous agent.
Watch for additional disclosures of AI‑driven attack techniques, particularly those that combine vulnerability exploitation with autonomous decision‑making.
Monitor Zammad’s patch releases and verify that the latest version addresses both CVEs, as the advisory notes a remaining privilege‑escalation issue in version 7 releases.
Observe any attribution efforts or threat‑intel reports that may link the to known threat actors, which could inform broader defensive postures.