How to fix CVE-2026-102489: Zammad GmbH Zammad (exploited in the wild)

Zammad versions 6.3.0 to 6.5.4 are vulnerable a session hijack vulnerability that leads to remote code execution as the zammad user. The bug is also present in version 7.0.0 to version 7.1.2, but not exploitable due to changes in the underlying framework.

• Severity: CRITICAL (CVSS 4.0 9.4, vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:A/AU:Y/V:C).
• Weakness: CWE-384.
• NVD published 2026-09-30, status Analyzed.

Anyone running Zammad GmbH Zammad in the version ranges below. Internet-facing instances are the priority.

• zammad zammad: from 6.3.0 up to and including 6.5.4.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

• Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-10-02; federal remediation due date 2026-10-05.
• Public proof-of-concept code: 3 GitHub repositories from 3 accounts, the first on 2026-10-06.

• EPSS (probability of exploitation activity in the next 30 days): 1.26%, higher than 69% of all scored CVEs (as of 2026-10-24).
• CVERadar threat level: 62/100 (see methodology).
• Likely ATT&CK techniques: T1203 Exploitation for Client Execution (inferred); T1190 Exploit Public-Facing Application (inferred).

1. Find every instance. List where Zammad GmbH Zammad runs, including test, DR and forgotten internet-facing systems, and record the installed version.
2. Apply the latest vendor update. NVD does not list a fixed version, so follow the vendor advisory for the patched release.
3. If you can't patch today, follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build. Re-scan from outside if the service is exposed.
5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

• T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to Zammad (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-09-30.
• T1203 Exploitation for Client Execution: Exploitation of client or server software usually shows as crashes of the affected process followed by unexpected child processes; check EDR alerts for both.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

• NVD: CVE-2026-102489 nvd.nist.gov/vuln/detail/CVE-2026-102489
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-102489
• Vendor link from CISA KEV zammad.com/en/product/releases/
• Vendor link from CISA KEV community.zammad.org/t/take-care-local-privilege-escalation-cve-2026-1
• Vendor Advisory zammad.com/en/advisories/cve-2026-102489-cve-2026-102490
• CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST EPSS (2026-10-24) api.first.org/data/v1/epss?cve=CVE-2026-102489