Zammad CVEs Allow Session Fixation to Root Under Active Exploitation
On October 2, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added two critical zero-day vulnerabilities in the open-source Zammad helpdesk platform to its Known Exploited Vulnerabilities (KEV) Catalog. The flaws — tracked as CVE-2026-102489 and CVE-2026-102490 — enable unauthenticated attackers to hijack sessions, execute remote code, and escalate privileges to root. Active exploitation has already been confirmed, including a high-profile breach of the Dutch Institute for Vulnerability Disclosure (DIVD) carried out by an autonomous AI agent.
What Happened: CISA Confirms Active Exploitation of Zammad Zero-Days
CISA added CVE-2026-102489 and CVE-2026-102490 to the KEV Catalog on October 2, 2026, giving federal agencies an unusually short remediation timeline. Furthermore, the agency confirmed evidence of active exploitation in the wild. The vulnerabilities were originally disclosed by DIVD in collaboration with Merlon Security on September 29, 2026.
The pair of flaws was chained together to breach DIVD itself. According to the nonprofit, an autonomous AI agent executed the attack chain in seconds. Consequently, the agent gained remote code execution as the Zammad user and then escalated to root privileges. DIVD described the intrusion as “loud and very, very messy.” The incident underscores the growing threat of AI-driven autonomous attacks against unpatched internet-facing systems.
Technical Details of the Zammad Vulnerability Chain
Zammad is an open-source customer support and ticketing platform used by small businesses, MSPs, and enterprises worldwide. It typically runs behind Nginx or Apache reverse proxies on ports 443 or 3000, with Elasticsearch and PostgreSQL backends. Because it is designed to be internet-accessible, the platform holds sensitive customer communications, email integrations, and password reset flows.
CVE-2026-102489: Session Fixation Leading to Remote Code Execution
This vulnerability carries a CVSS base score of 9.8 and affects Zammad versions 6.3.0 through 6.5.4. The flaw is also present in versions 7.0.0 through 7.1.3, though it is not exploitable in that range due to environmental conditions.
The attack works as follows:
- The attacker obtains or plants a pre-authentication session identifier.
- The victim clicks a crafted link and authenticates normally.
- The application fails to rotate the session ID after authentication.
- The attacker presents the known session cookie and inherits the authenticated session.
- From there, the attacker achieves remote code execution as the zammad system user.
This technique bypasses password complexity and, in many implementations, defeats multi-factor authentication because the session is hijacked after successful authentication.
CVE-2026-102490: Improper Privilege Management to Root
This second flaw, also rated critical, affects all versions of Zammad including the latest alpha release. It allows the low-privilege zammad user to escalate privileges to root on the underlying system. When chained with CVE-2026-102489, the attacker achieves a complete compromise: from unauthenticated network access to full root control.
The realistic attack chain is devastating in its simplicity:
- Attacker fixates a session for a victim user.
- Victim logs in and the attacker hijacks the authenticated session.
- Attacker abuses privilege management flaws to assign themselves an admin role.
- Attacker then leverages CVE-2026-102490 to escalate from zammad user to root.
Business and Operational Impact
The exploitation of these flaws poses severe consequences for organizations running Zammad. The following impacts are most critical:
- Complete system compromise: Root access grants attackers full control over the server and any connected systems.
- Data exfiltration: Helpdesk tickets often contain credentials, password reset links, and internal communications.
- Service disruption: Attackers can tamper with workflows, delete data, or deploy ransomware.
- Lateral movement: Zammad integrations with LDAP, Active Directory, and email systems provide pathways into internal networks.
- Compliance implications: Breaches of customer support data may trigger GDPR, HIPAA, or other regulatory reporting obligations.
Moreover, the confirmed AI-driven nature of the DIVD breach suggests that exploitation can occur autonomously and at machine speed. Therefore, manual patching timelines that were once acceptable may now be dangerously slow.
Mitigation and Recommendations
Immediate Actions for Defenders
- Patch immediately: Upgrade all Zammad instances to version 7.2.0 or later. The vendor has released fixes that address both vulnerabilities.
- Verify version: Run
zammad run rails r 'puts Zammad::VERSION'or check the admin console footer. - Hunt for indicators: Review web server and application access logs for unusual session activity tied to the zammad user account.
- Deploy WAF rules: Use a Web Application Firewall to filter malicious session-related payloads.
- Restrict network exposure: If patching is not immediately possible, isolate internet-facing Zammad instances behind a VPN or restrict access to trusted IP ranges.
Long-Term Measures
Organizations should adopt risk-based vulnerability management practices as encouraged by CISA. Furthermore, they should integrate KEV Catalog checks into their vulnerability management workflows. For Zammad specifically, ensure session management hardening is in place and monitor for anomalous privilege escalation attempts.
Bottom line: These are not theoretical vulnerabilities. CISA has confirmed active exploitation, a real-world AI-driven breach has occurred, and the attack chain is both simple and devastating. Patch now.
Incident Summary
| CVE ID / Incident: | CVE-2026-102489 (Session Fixation → RCE) and CVE-2026-102490 (Privilege Escalation → Root) |
| Affected Systems: | Zammad open-source helpdesk versions 6.3.0–6.5.4 (CVE-2026-102489); all versions including latest alpha (CVE-2026-102490) |
| Disclosure Date: | September 29, 2026 (DIVD/Merlon Security); October 2, 2026 (CISA KEV addition) |
| Patch Status: | Fixed in Zammad 7.2.0+; upgrade immediately |
| CVSS Score: | 9.8 Critical (both CVEs) |
| CISA KEV Added: | October 2, 2026 |
References
- CISA, “CISA Adds Two Known Exploited Vulnerabilities to Catalog,” October 2, 2026, https://www.cisa.gov/news-events/alerts/2026/10/02/cisa-adds-two-known-exploited-vulnerabilities-catalog, accessed October 4, 2026.
- DIVD Case File, “DIVD-2026-00015 — Zammad Session Fixation and Privilege Escalation,” September 29, 2026, https://csirt.divd.nl/DIVD-2026-00015, accessed October 4, 2026.
- CVE Brief, “CVE-2026-102489 Analyst Report,” October 2, 2026, https://cvebrief.com/cve/cve-2026-102489/, accessed October 4, 2026.
- CVETodo, “Zammad Zero-Days CVE-2026-102489 and CVE-2026-102490 Exploited in AI-Driven Breach of DIVD,” October 2026, https://cvetodo.com/news/zammad-zero-days-cve-2026-102489-and-cve-2026-102490-exploited-in-ai-driven-breach-of-cybersecurity-, accessed October 4, 2026.
- Security Arsenal, “CISA KEV Alert: Zammad CVE-2026-102489 & CVE-2026-102490,” October 2, 2026, https://securityarsenal.com/blog/cisa-kev-alert-zammad-cve-2026-102489-and-cve-2026-102490-session-fixation-and-privilege-escalation-under-active-exploitation, accessed October 4, 2026.
- NIST NVD, “CVE-2026-102489 Detail,” https://nvd.nist.gov/vuln/detail/CVE-2026-102489, accessed October 4, 2026.
- NIST NVD, “CVE-2026-102490 Detail,” https://nvd.nist.gov/vuln/detail/CVE-2026-102490, accessed October 4, 2026.