Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-102489: Zammad WebSocket Session Disclosure Leading to Remote Code Execution

Published Sep 30, 2026 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days11 mentions · peak 2 in a dayToday
CVSS9.4Critical · v4
EPSS49.9%99th percentile
CISA KEVYesAdded Oct 2, 2026
In the wildActivePer CISA KEV
Vendor
Zammad
IdentifiersCVE-2026-102489CWE-209

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

3 exploits validated by Mallory's analysis.

View more in app →
CVE-2026-102489The supplied repository contains two files: a standalone Python exploit (7,574 bytes) and a README (2,706 bytes). The Python script embeds a Ruby ERB command-execution payload; no exploit framework, dependency manifest, or tests are present. It sends an unauthenticated WebSocket event named base, expecting a Ruby NoMethodError to disclose the shared @clients map and connected users' session cookies. It validates those cookies through the users/me API, preferentially selects a session containing role ID 1, obtains a CSRF token, and uploads the ZammadRceAddon package containing a malicious password-reset mailer template. A password-reset request then attempts to execute the operator's command, defaulting to id, as the Zammad service user. Cleanup attempts package removal but suppresses exceptions and does not explicitly remove the output file. The script reports execution after a fixed delay without verifying output, so its success messages are not proof of compromise. HTTP requests disable TLS certificate verification. No reverse shell, external exfiltration destination, or direct command-output retrieval is implemented. The repository claims CVE-2026-102489 affects Zammad <= 6.5.4 and is fixed in 7.2.0; these claims and runtime exploitability cannot be independently verified from the supplied files. The Git reference and archive size were not supplied: ref is empty and size_bytes is 0 to represent unavailable metadata; the listed file sizes total 10,280 bytes.horizon3ai · Disclosed Oct 6, 2026 · python · ruby · network · webOperationalCVE-2026-102489The repository contains five files: a standalone Go exploit program, README documentation, Go module and checksum files, and a .gitignore. Its only declared external dependency is github.com/gorilla/websocket v1.5.3. The visible program discovers the Zammad session-cookie name, opens /ws with a fabricated cookie, sends a base event, and parses error messages for Ruby-style Cookie headers. It extracts hexadecimal session values of at least 20 characters and begins checking their identities through /api/v1/users/me. The documented next stages select an administrator session, upload an addon that overwrites an English password-reset ERB template, and trigger the mailer to execute a command. Observable package identifiers include the prefix ZammadRceAddon and version 1.0.0. The CLI supports single targets or target lists, configurable commands and output paths, verbosity, and delays between targets; HTTP and WebSocket TLS certificate verification is disabled. This is an exploitation tool rather than a detection-only script, with no visible destructive local behavior or unrelated exfiltration destination. However, the supplied zammad.go content is truncated through the central exploitation logic, preventing verification of administrator selection, package construction, command execution, cleanup, or output retrieval. The CVE identifier, affected-version range, and fix version are repository claims, not independently established facts. The repository URL is inferred from go.mod; no Git reference or archive size was supplied, so the reference is empty and size_bytes is an unknown-value placeholder. Listed file sizes total 14,440 bytes, which is not an archive-size measurement.1xPwn · Disclosed Oct 11, 2026 · go · network · webOperationalthe-cookie-in-the-error-message-cve-2026-102489-zammad-session-hijack-to-rceThe repository contains six files: one README, three Ruby programs, and two POSIX shell scripts. It is a standalone laboratory reproduction, not a framework module or a working exploit against live Zammad. minibox_server.rb replaces WebSocket framing with newline-delimited JSON over TCP, keeps every connected client's handshake headers in a shared registry, deliberately invokes the nonexistent registry method foo, logs e.inspect, and returns e.message to the requesting client. On a Ruby runtime that includes the hash receiver in the exception text, this exposes other clients' cookies. minibox_attack.rb creates both the synthetic victim and unauthenticated attacker, sends the trigger event, extracts the hardcoded victim cookie's token, and submits a login event with that token. The server's fake session store then associates the attacker connection with admin@example.com. The actual production event needed to trigger the exception is explicitly undisclosed, and no RCE or post-exploitation payload is supplied. ruby_behavior_probe.rb isolates the exception-rendering dependency and exits with status 1 when cookie material appears. ioc_check.sh searches ordinary and compressed logs for ERROR lines containing a Cookie hash entry or @clients registry, reports matching lines, and prints distinct exposed cookies. It returns status 0 whether indicators are present or absent, so automation must inspect its output. ioc_check_test.sh feeds it a synthetic matching log line and conditionally downloads the scanner if missing; it does not assert the result. Its rm -rf operation is scoped to a generated temporary directory and is ordinary cleanup, not evidence of a fake exploit. Important limitations include a possible timing race between registration of the victim connection and the attacker's trigger, hardcoded token extraction, and loopback-only server binding, which also means the README's published-port Docker example does not by itself make the service reachable through the container interface. The README attributes CVE-2026-102489 to Zammad 6.3.x–6.5.x and claims a subsequent RCE chain, real-world exploitation, and KEV inclusion; these external claims are not verified by the supplied files. Repository URL, revision, and archive size were not supplied; the listed file sizes total 19,462 bytes, which is not an archive-size measurement.Hunt-Benito · Disclosed Oct 7, 2026 · ruby · bash · networkPoC
Exposure surface

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.

VendorProductType
ZammadZammadapplication
FAQ

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.
Activity feed

Recent activity

132 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+37 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity87Community discussion across Reddit, Mastodon, and other social sources.