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

Zammad packages built with packager.io (DEB and RPM) could have allowed a local attacker who already had file system write privileges as the unprivileged zammad service account to escalate to full root privileges on the host. Service processes began running as root and executed files that were owned and writable by the zammad account before dropping their identity to that account. An attacker holding that foothold could have escalated within seconds, because the affected services were restarted automatically whenever they stopped; no administrator interaction was required. Only installations from the DEB and RPM packages were affected — installations from source or the official container images were not. All released packaged versions were affected.

• 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-269.
• 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: up to (not including) 7.2.2.

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.

• EPSS (probability of exploitation activity in the next 30 days): 0.55%, higher than 45% of all scored CVEs (as of 2026-10-24).
• CVERadar threat level: 62/100 (see methodology).
• Likely ATT&CK techniques: T1068 Exploitation for Privilege Escalation (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. Upgrade to a fixed release. zammad zammad: 7.2.2 or later. Get the build from the vendor advisory.
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 (7.2.2 or later). 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

• T1068 Exploitation for Privilege Escalation: Alert on processes gaining SYSTEM/root unexpectedly, and review who holds admin rights.

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

• NVD: CVE-2026-102490 nvd.nist.gov/vuln/detail/CVE-2026-102490
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-102490
• 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 github.com/zammad/zammad/security/advisories/GHSA-p97w-927q-8vxq
• 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-102490