CVE-2026-102489: Zammad WebSocket Session Disclosure Leading to Remote Code Execution
- Vendor
- Zammad
CVE-2026-102489 is an unauthenticated session-disclosure vulnerability in Zammad's WebSocket event handling that can lead to remote code execution. A crafted base event instantiates Sessions::Event::Base with a shared registry containing active connections and their request headers. Calling the unimplemented run method raises a Ruby NoMethodError whose message includes the event object's internal state, exposing connected users' session cookies to the requester. Replaying a disclosed cookie permits session hijacking. An administrator session allows abuse of package installation to replace an email template with malicious ERB code, which executes as the Zammad service account when rendered. Zammad versions 6.3.0 through 6.5.4 are reported exploitable, although structured version records inconsistently exclude 6.5.4. The affected code also exists in early 7.x releases, reported through 7.1.3, but framework or runtime changes prevent exploitation in those releases.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An unauthenticated attacker can impersonate connected users and access or modify information available to their sessions, including support tickets, customer records, and application-accessible credentials. Compromise of an administrator session can lead to arbitrary code execution as the low-privileged Zammad operating-system account, affecting application confidentiality, integrity, and availability. This vulnerability does not independently grant root privileges. Attackers exploited it alongside CVE-2026-102490 during the September 21, 2026 DIVD breach to obtain root access and exfiltrate data. CISA added CVE-2026-102489 to its Known Exploited Vulnerabilities catalog on October 2, 2026.
Mitigation
If you can’t patch tonight, do this now.
Take vulnerable installations offline if upgrading is not immediately possible; no application-level workaround is documented. Restrict network access to the helpdesk, isolate it from internal services, and block unnecessary outbound traffic to reduce exposure and post-exploitation reach. Preserve application, web-server, and network logs before upgrades or rebuilding. Run DIVD's log-checking script and investigate evidence of session disclosure, unexpected service-account commands, privilege escalation, or data transfers; an absence of matching log entries does not exclude compromise. If exploitation is identified, treat the host as compromised and rotate accessible credentials.
Remediation
Patch, then assume compromise.
Upgrade to Zammad 7.2.0 or a later supported release; version 7.2.0 includes hardening of the affected code. Versions 7.0 and later prevent the demonstrated exploitation through framework or runtime changes, but upgrading to a current supported release is preferable. Do not treat 6.5.4 as a confirmed fixed version because affected-version records conflict. Zammad 6.5 and earlier are unsupported. Address CVE-2026-102490 separately, since blocking this initial access vulnerability does not remove the local privilege-escalation risk or eradicate an existing compromise.
Exploits
3 exploits validated by Mallory's analysis.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-102489 exploited in the wild?
- Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 2, 2026.
- Is there a public exploit for CVE-2026-102489?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-102489, the earliest disclosed Oct 6, 2026.
- Is there a patch for CVE-2026-102489?
- Upgrade to Zammad 7.2.0 or a later supported release; version 7.2.0 includes hardening of the affected code. Versions 7.0 and later prevent the demonstrated exploitation through framework or runtime changes, but upgrading to a current supported release is preferable.
- What products are affected by CVE-2026-102489?
- Zammad.
- How severe is CVE-2026-102489?
- CVE-2026-102489 has a CVSS v4 score of 9.4 (Critical) and an EPSS score of 49.9% (99th percentile) as of Nov 17, 2026.
Recent activity
132 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.