Threat reportVulnerabilityTL-2026-2843
CISA adds two Zammad vulnerabilities to KEV: CVE-2026-102489 (session fixation to RCE) and CVE-2026-102490 (local privilege escalation to root), chained in an agentic-AI attack on DIVD
On 2026-10-02 CISA added CVE-2026-102489 (session fixation leading to RCE as the zammad user) and CVE-2026-102490 (zammad-to-root privilege escalation) in Zammad to the KEV catalog. The two flaws were chained as zero-days on 2026-09-21 to breach the Dutch Institute for Vulnerability Disclosure (DIVD), in what DIVD describes as an agentic AI-powered attack.
Key facts
| Identifiers | TL-2026-2843, CVE-2026-102489, CVE-2026-102490 |
|---|---|
| Also known as | DIVD-2026-00015, DIVD-2026-00014 |
| Severity | CRITICAL |
| CVSS | 9.8 |
| Exploitation status | Linked CVE exploited in the wild; Listed in CISA KEV: CVE-2026-102489 (added ), CVE-2026-102490 (added ) |
| EPSS | CVE-2026-102489: 1.2% (68.6th percentile); CVE-2026-102490: 0.5% (44.3th percentile) |
| Affected products | Zammad GmbH Zammad (CVE-2026-102489, session fixation to RCE); Zammad GmbH Zammad on Linux and Docker (CVE-2026-102490, zammad-to-root privilege escalation) |
| Weaknesses (CWE) | CWE-384, CWE-269, CWE-280 |
| Tools | Autonomous AI agent (undisclosed model/framework) |
| MITRE ATT&CK techniques | T1005 Data from Local System, T1021 Remote Services, T1041 Exfiltration Over C2 Channel, T1059 Command and Scripting Interpreter, T1059.004 Command and Scripting Interpreter: Unix Shell, T1068 Exploitation for Privilege Escalation, T1070 Indicator Removal, T1083 File and Directory Discovery, T1087 Account Discovery, T1110.003 Brute Force: Password Spraying, T1190 Exploit Public-Facing Application, T1213 Data from Information Repositories and 5 more in the attack flow |
| Motivation | UNKNOWN |
| Target sectors | technology, government administration, non-profit organisation, customer-support |
| Target regions | Global, Europe |
| Detection rules | 9 (1 shown free) |
| Sources | 13 cited sources |
Detection coverage
As of 2026-10-09, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2843 across Splunk SPL, Microsoft KQL and Sigma, covering 29 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Zammad Application Process Spawning Shell, Interpreter or Download Utility (CVE-2026-102489 RCE)
Detects the Zammad web/application process (puma/ruby/bundle/rails) running as the zammad OS user spawning a shell, interpreter or download utility. This is the observable outcome of CVE-2026-102489 (session fixation to RCE as the zammad user), exploited as a zero-day against DIVD on 2026-09-21 and added to CISA KEV on 2026-10-02. Exact exploit requests are unpublished, so this rule keys on the post-exploit process lineage rather than a request signature. curl/wget children additionally indicate ingress tool transfer (T1105) and python/perl children indicate script interpreter abuse.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1190, T1059.004, T1059.006, T1105
- Data sources: sysmon_for_linux, defender_for_endpoint_linux, linux_auditd
- Severity: critical
- Confidence: high
Splunk SPL
```Zammad web process (puma/ruby) spawning a shell or downloader = RCE as the zammad user```
index=linux sourcetype="sysmon:linux" (EventID=1 OR EventCode=1) User="zammad"
(ParentImage="*/ruby" OR ParentImage="*/puma" OR ParentImage="*/bundle" OR ParentImage="*/rails" OR ParentCommandLine="*puma*" OR ParentCommandLine="*rails server*")
(Image="*/sh" OR Image="*/bash" OR Image="*/dash" OR Image="*/curl" OR Image="*/wget" OR Image="*/nc" OR Image="*/ncat" OR Image="*/python" OR Image="*/python3" OR Image="*/perl")
| eval transfer_tool=if(match(Image,"/(curl|wget)$"),1,0)
| stats count min(_time) as first_seen max(_time) as last_seen dc(Image) as distinct_children max(transfer_tool) as ingress_tool_transfer values(Image) as child_images values(CommandLine) as commands by host User ParentImage ParentCommandLine
| convert ctime(first_seen) ctime(last_seen)Microsoft KQL
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessAccountName =~ 'zammad'
| where InitiatingProcessFileName in~ ('ruby','puma','bundle','rails') or InitiatingProcessCommandLine has_any ('puma','rails server')
| where FileName in~ ('sh','bash','dash','curl','wget','nc','ncat','python','python3','perl')
| extend IngressToolTransfer = FileName in~ ('curl','wget')
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, IngressToolTransfer, InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessParentFileName
| order by Timestamp descSigma
title: Zammad Application Process Spawning Shell or Download Utility
id: 2f9a4c68-1b3d-4e75-8c02-6d7e5a1f9b43
status: experimental
description: Detects the Zammad application process (ruby, puma, bundle, rails) running as the zammad user spawning a shell, interpreter or download utility, the outcome of CVE-2026-102489 session fixation to RCE.
references:
- https://csirt.divd.nl/cases/DIVD-2026-00015/
- https://www.cisa.gov/news-events/alerts/2026/10/02/cisa-adds-two-known-exploited-vulnerabilities-catalog
author: Threadlinqs Team
date: 2026-10-02
tags:
- attack.initial-access
- attack.t1190
- attack.execution
- attack.t1059.004
- attack.t1059.006
- attack.command-and-control
- attack.t1105
- cve.2026.102489
logsource:
category: process_creation
product: linux
detection:
selection_user:
User: zammad
selection_parent:
ParentImage|endswith:
- '/ruby'
- '/puma'
- '/bundle'
- '/rails'
selection_child:
Image|endswith:
- '/sh'
- '/bash'
- '/dash'
- '/curl'
- '/wget'
- '/nc'
- '/ncat'
- '/python'
- '/python3'
- '/perl'
condition: all of selection_*
falsepositives:
- Zammad shelling out to helper binaries during normal operation (image conversion, text extraction)
- Administrators running zammad run rails console and invoking system commands
level: highKnown false positives:
- Zammad legitimately invoking helper binaries through /bin/sh during attachment processing
- Administrator running a rails console from a service-account session that shells out
Tuning notes: Baseline child processes of the Zammad ruby/puma worker for 7 days and allow-list known helper command lines (ImageMagick, pdftotext) by exact CommandLine. ParentImage paths differ between package installs (/opt/zammad/vendor/ruby-*/bin/ruby) and Docker; confirm with a sample event. Sysmon for Linux must be configured with ProcessCreate rules covering the zammad user; auditd execve can substitute.
- [indicator] Session Cookie Reused From Multiple Source IPs (Session Hijack) · unlock with TL Creds
- [indicator] Service Account Privilege Escalation Reconnaissance · unlock with TL Creds
- Adversary-in-the-Middle Tooling Execution Near Helpdesk Infrastructure · unlock with TL Creds
- Reverse Shell or Download Cradle Run by [indicator] Service Account · unlock with TL Creds
- [indicator] Data Collection, Credential Config Reads and Staging Archives · unlock with TL Creds
- Machine-Speed Command Burst by [indicator] Service Account (Agentic Attacker Pattern) · unlock with TL Creds
- [indicator] Service Account Escalating to Root or Abusing Sudo/Setuid (CVE-2026-102490 Local Privilege Escalation) · unlock with TL Creds
- [indicator] Sign-in Endpoint Password Spraying Burst With Successful Login · unlock with TL Creds
Indicators of compromise
As of 2026-10-09, Threadlinqs Intelligence tracks 29 indicators of compromise for TL-2026-2843.
Sample indicators (1 of 29)
- URL:
hxxps://github[.]com/horizon3ai/CVE-2026-102489
Defanged, TLP:CLEAR. Full set of 29 indicators: unlock with TL Creds.
Technical analysis
Zammad is an open-source web helpdesk and ticketing system. CVE-2026-102489 is a session fixation / session hijack flaw (CWE-384) in Zammad 6.3.0 through 6.5.4 that leads to remote code execution as the local zammad OS user. Versions 7.0.0 through 7.1.3 contain the defect but, per DIVD and the vendor, are not practically exploitable because of the runtime environment those releases use; the vendor states exploitation is only possible on Zammad 6.5 and older and that the issue is addressed in 7.2.0. CVE-2026-102490 (CWE-269, improper privilege management) lets the local zammad user escalate to root and is reported to affect Zammad 1.5.0 through 7.1.0-alpha on Linux and Docker. It cannot be exploited remotely on its own, but CISA's KEV entries state each can be chained with the other, turning an unauthenticated network attack into full operating-system compromise.
Both flaws were exploited as zero-days against DIVD's own Zammad instance. Initial malicious access occurred on 2026-09-21; DIVD detected the activity on 2026-09-22, blocked access, and engaged Merlon Security for forensics. DIVD reproduced the issues within about 24 hours during case DIVD-2026-00014 (the breach) and opened DIVD-2026-00015 (the Zammad vulnerabilities) for victim notification. DIVD reports the progression from session hijack to root took seconds and attributes the speed and behaviour to an autonomous AI agent: attack logs and scripts contained self-justifying comments, the agent decided each next step itself, and it polluted its own man-in-the-middle attempt with password spraying. Reported data exposure includes DIVD volunteer email addresses and possibly contact details; network segmentation reportedly contained the attacker and prevented persistent footholds. No attacker IPs, domains, hashes or user agents have been published.
There is a vendor/researcher dispute: Zammad states DIVD has not provided technical details for CVE-2026-102490, objects to the disclosure timeline, and as of its 2026-10-01 statement and the runZero write-up no official patch was announced for CVE-2026-102490, while one secondary source claims it is fixed from 7.1.0-alpha onward; treat the fix status of CVE-2026-102490 as unconfirmed. CVSS values vary by source: NVD lists 9.8 (v3.1) and 9.4 (v4.0) for both CVEs, while runZero cites 8.7 and 8.5 (CVSS v4) for the individual flaws and 9.4 for the chain. CISA marks Known Ransomware Campaign Use as Unknown, requires forensic triage, and set a due date of 2026-10-05 under BOD 26-04.
MITRE ATT&CK techniques by tactic:
Collection
T1005 Data from Local System; T1213 Data from Information Repositories
Lateral Movement
Exfiltration
T1041 Exfiltration Over C2 Channel
Execution
T1059 Command and Scripting Interpreter; T1059.004 Command and Scripting Interpreter: Unix Shell
Privilege Escalation
T1068 Exploitation for Privilege Escalation; T1548 Abuse Elevation Control Mechanism
Defense Evasion
T1070 Indicator Removal; T1550.004 Use Alternate Authentication Material: Web Session Cookie
Discovery
T1083 File and Directory Discovery; T1087 Account Discovery
Credential Access
T1110.003 Brute Force: Password Spraying; T1539 Steal Web Session Cookie; T1552.001 Unsecured Credentials: Credentials In Files; T1557 Adversary-in-the-Middle
Initial Access
Remediation
Patches
- CVE-2026-102489: addressed in Zammad 7.2.0 (7.0+ not practically exploitable)
- CVE-2026-102490: no official patch confirmed as of 2026-10-01; fix status disputed between DIVD and vendor
Immediate actions
- Upgrade Zammad to 7.2.0 or later (current stable); versions 6.5 and earlier are end-of-support and receive no security fixes
- If an upgrade is not possible, take the Zammad instance offline or remove internet exposure (CISA: discontinue use if mitigations are unavailable)
- Run DIVD's log check script (cve-2026-102489_ioc_check_script_v2.sh) against Zammad logs to look for indicators of compromise
- Preserve application, web server, authentication and system logs and perform forensic triage as CISA requires; treat any exposed 6.3.0-6.5.4 instance as potentially compromised to root
- Rotate credentials and secrets reachable from the Zammad host
Workarounds
- Take the instance offline until upgraded
- Review logs for suspicious sessions, unexpected administrative activity and command execution as the zammad user, and for the zammad user spawning root processes
Longer-term hardening
- Segment helpdesk infrastructure from other services so a Zammad compromise cannot reach adjacent systems (segmentation contained the DIVD intrusion)
- Inventory Zammad deployments (dpkg -l zammad, rpm -q zammad, docker image listing) and restrict the UI from the internet unless required
- Monitor the Zammad GitHub security advisories for the CVE-2026-102490 fix status
Affected and fixed versions
- Zammad GmbH — Zammad (CVE-2026-102489, session fixation to RCE)
Vulnerable versions: 6.3.0 through 6.5.4 (exploitable); 7.0.0 through 7.1.3 (defect present, not practically exploitable)
Fixed in: 7.2.0 - Zammad GmbH — Zammad on Linux and Docker (CVE-2026-102490, zammad-to-root privilege escalation)
Vulnerable versions: 1.5.0 through 7.1.0-alpha
Timeline
Last updated · 5 updates · revalidated 5× · latest source
- Attacker gains initial access to DIVD's Zammad instance by chaining CVE-2026-102489 and CVE-2026-102490 as zero-days; the progression from session hijack to root takes seconds.
- DIVD detects the malicious activity, blocks access, and engages Merlon Security for incident response and forensics.
- Zammad releases version 7.2.0, which the vendor says includes hardening of the affected code.
- DIVD analyses and reproduces both vulnerabilities (analysis spanned 2026-09-22 to 2026-09-23).
- DIVD publicly discloses the breach via LinkedIn on the same day it reports the vulnerabilities to Zammad.
- DIVD reports the vulnerabilities to Zammad.
- Case DIVD-2026-00015 opened and CVE IDs assigned; DIVD begins internet scanning and notifying owners of exposed Zammad instances.
- CVE-2026-102489 and CVE-2026-102490 records and DIVD advisories published.
- NCSC-NL publishes advisory NCSC-2026-0396 and an alert on active exploitation of the Zammad zero-days, dating exploitation to at least 2026-09-21; no patch for CVE-2026-102490 reported at that time.
- DIVD publicly identifies the two Zammad zero-days as the attack vector for its breach and describes the attack as agentic AI-powered.
- DIVD confirms data was read and exfiltrated from the compromised helpdesk host (volunteer email addresses); Sysdig additionally reports partial extraction of CSIRT ticketing emails and access to a project support environment (Jira, Confluence).
- Zammad publishes its security statement: CVE-2026-102489 addressed in 7.2.0, no technical details received for CVE-2026-102490, and it objects to the disclosure timeline; DIVD publishes its data-breach overview.
- CISA adds CVE-2026-102489 and CVE-2026-102490 to the KEV Catalog citing evidence of active exploitation.
- Zammad publishes its advisory: CVE-2026-102489 fixed in 7.2.0; CVE-2026-102490 fix still under development with no release date.
- CISA KEV remediation due date for both CVEs under BOD 26-04.
- Horizon3.ai publishes its technical root-cause analysis and a public PoC (locked-ioc-8) for CVE-2026-102489: WebSocket session cookie leak, admin session hijack, malicious ERB package install, RCE as the zammad user.
Update history
- 2026-10-09 — Zammad WebSocket Session Leak Enables Session Hijacking and RCE (CVE-2026-102489), Chained with Root LPE (CVE-2026-102490): What changed No whitelisted field escalation (severity CRITICAL and exploitability ACTIVE already set).
- 2026-10-08 — CVE-2026-102489: Zammad Unauthenticated WebSocket Session Disclosure Exploited in the Wild, Chained with CVE-2026-102490 to Root (CISA KEV): What changed No severity, exploitability or status change (already CRITICAL / ACTIVE).
- 2026-10-05 — Zammad Zero-Days (CVE-2026-102489, CVE-2026-102490) Chained for Session Hijack RCE and Root Escalation; Exploited in the DIVD Breach: What changed No severity, exploitability or status change. Existing record already CRITICAL / ACTIVE. New indicators (1) Indicator values are withheld at this access level.
- 2026-10-04 — Zammad 0-Day Chain (CVE-2026-102489 Session Hijack to RCE + CVE-2026-102490 Local Root Escalation) Exploited by Autonomous AI Agent to Breach DIVD: What changed No severity, exploitability, status or CVSS change; existing values (CRITICAL / ACTIVE / 9.8) already match the newer report.
- 2026-10-03 — Zammad session fixation RCE (CVE-2026-102489) and local privilege escalation to root (CVE-2026-102490) exploited as zero-days by an AI agent against DIVD; added to CISA KEV: What changed No severity/exploitability/status change (already CRITICAL/ACTIVE). Scope of impact expanded: data exfiltration confirmed and post-compromise access to other internal services reported.
Sources cited
- CISA Adds Two Known Exploited Vulnerabilities to Catalog CISA · Government advisory · 2026-10-02
- CISA Known Exploited Vulnerabilities Catalog (JSON feed) CISA · Government advisory · 2026-10-02
- NVD - CVE-2026-102489 NVD (NIST) · Advisory · 2026-10-02
- NVD - CVE-2026-102490 NVD (NIST) · Advisory · 2026-10-02
- DIVD-2026-00015 - Vulnerabilities in Zammad during investigation of case DIVD-2026-00014 csirt.divd.nl · Research · 2026-09-26
- DIVD-2026-00014 - DIVD incident case csirt.divd.nl · Research · 2026-09-29
- Zammad community: Take care - Local Privilege Escalation (CVE-2026-102490) is reported as being actively exploited community.zammad.org · Vendor report · 2026-10-01
- Zammad Security Advisories zammad.com · Vendor report · 2026-04-08
- runZero: Zammad vulnerabilities - Find impacted installations runzero.com · Blog · 2026-10-02
- HOL: Zammad session fixation to root hits CISA KEV hol.org · Blog · 2026-10-02
- SecurityOnline: Zammad Zero-Day Chain CVE-2026-102489 Exploited in the Wild in AI-Driven DIVD Breach securityonline.info · News · 2026-10-02
- Cybersecurity News: Zammad 0-Day Vulnerabilities Exploited to Gain Remote Code Execution and Root Access cybersecuritynews.com · News · 2026-10-02
- Forkast: An Autonomous AI Agent Just Breached a Vulnerability Disclosure Nonprofit by Chaining Two Zammad Zero-Days forkast.news · News · 2026-10-01
Other reports on CVE-2026-102489
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 13 sources; published ; last updated .