Zammad session fixation to root hits CISA KEV

4 min read

CVE-2026-102489 is not practically exploitable on Zammad 7.x. For CVE-2026-102490, upgrade self-hosted DEB/RPM packages to 7.2.2 or later.

Zammad session fixation to root hits CISA KEV
On this page

CISA added CVE-2026-102489 and CVE-2026-102490 to the Known Exploited Vulnerabilities catalog today (2026-10-02). The pair is a chain in the open-source Zammad helpdesk: session fixation that can reach remote code execution as the zammad user, then local privilege escalation from that user to root. CISA notes the two can be chained. KEV due date is 2026-10-05. Required action follows BOD 26-04 (risk-based patching plus forensic triage where applicable). Catalog version is 2026.10.02.

DIVD published the CVEs under case DIVD-2026-00015 after investigating its own network breach (case DIVD-2026-00014). DIVD says the chain was used in an automated attack against its Zammad instance. This page is the operator write-up from CISA KEV, the DIVD CVE records, and Zammad's community guidance. The HOL Guard evidence pack for CVE-2026-102489 is the linked source record (sibling CVE-2026-102490).

What breaks

CVE-2026-102489 (session fixation to RCE as zammad): DIVD rates CVSS 4.0 base 8.7 High (critical sibling vector 9.4). Attack vector is network, privileges none, user interaction passive, exploit maturity Attacked. DIVD marks Zammad 6.3.0 through versions before 6.5.4 as affected on Linux/Docker. Versions 7.0.0 and later are listed unaffected for practical exploitation; DIVD and Zammad both say the defect is present on some 7.x trains but not exploitable under those runtime conditions. Zammad states it hardened the code in 7.2.0.

CVE-2026-102490 (local privilege escalation to root): DIVD rates CVSS 4.0 base 8.5 High (critical sibling vector 9.4). Attack vector is local: an attacker who already runs as the zammad OS user can escalate to root. DIVD's original scope listed 1.5.0 before 7.1.0-alpha. Zammad's October 8 advisory confirms DEB/RPM packages built with packager.io through 7.2.1 were affected and 7.2.2 fixes the local privilege escalation. Official Zammad containers and source installs were not affected. The issue requires local access as the zammad user; it is not remotely exploitable on its own. CISA's KEV row explicitly says it can be chained with CVE-2026-102489.

Together: network path into RCE as zammad, then root on the host. That is why CISA put both on KEV the same day with a three-day due date.

Who is not in scope

  • Zammad 7.0+ for CVE-2026-102489 exploitation per DIVD product status and Zammad's 2026-10-01 statement: the session-to-RCE path is not practically exploitable on current 7.x runtime. Version 7.2.0 contains hardening for CVE-2026-102489, but DEB/RPM installations need 7.2.2 or newer to fix CVE-2026-102490.
  • Hosts where the attacker cannot reach the Zammad HTTP(S) UI and also cannot obtain a local zammad shell. The LPE alone is not a remote worm.
  • Non-Zammad helpdesks (Zendesk, Freshdesk, osTicket, and so on). These CVE IDs are Zammad GmbH Zammad only.
  • Zammad hosted SaaS is not affected by the DEB/RPM packager.io vulnerability, according to the October 8 vendor release. Self-hosted DEB/RPM installations need 7.2.2+; official containers and source installations are not affected by this LPE.

One operator check

On each self-hosted box, confirm the installed package version and whether the service is internet-facing:

# Debian/Ubuntu package installs
dpkg -l zammad | awk 'NR==1 || /^ii/'

# RPM installs
rpm -q zammad

# Docker / compose: inspect the image tag you actually run
docker ps --format '{{.Image}}' | grep -i zammad

# Confirm the UI listener is not on the public internet unless required
ss -lntp | egrep ':80|:443' 

If a DEB/RPM installation runs 7.2.1 or earlier, upgrade to 7.2.2 or newer for CVE-2026-102490. Official containers and source installations are not affected by this package-only flaw; keep them on a supported release. Federal and BOD 26-04 environments also owe forensic triage before they declare the host clean; KEV due date is 2026-10-05.

How to fix

Zammad's October 8 release fixes CVE-2026-102490 in 7.2.2 for DEB/RPM installs. Version 7.2.0 hardened the separate CVE-2026-102489 path, which the vendor says is not practically exploitable on 7.x. Zammad 6.5 and older remain out of support and require an upgrade.

# Package-based self-host (follow your distro docs for the Zammad repo)
sudo apt-get update && sudo apt-get install --only-upgrade zammad
# or
sudo yum update zammad

# Then confirm
dpkg -l zammad
# expect 7.2.2 or newer for DEB/RPM installations

Official container images and source installations were not affected by this package-only LPE. Keep them on a supported release for other security updates. The exact package scope is in Zammad's published advisory.

Until DEB/RPM systems are patched to 7.2.2, restrict access to the underlying host to trusted administrators. Limiting UI exposure may reduce remote risk but does not fix a local privilege escalation when the attacker already runs as zammad.

What this is not

This is not a mass internet worm that needs no user interaction on every Zammad 7.x box. CVE-2026-102489's practical blast is the EOL 6.5 train (and DIVD's stated 6.3.0-before-6.5.4 window). CVE-2026-102490 is local-as-zammad to root, not unauthenticated remote root by itself. It also is not "wait for a detailed Zammad PSIRT write-up before acting": CISA already listed both CVEs with due date 2026-10-05, and Zammad's October 8 release now identifies 7.2.2 as the package-only LPE fix.

References

October 8 patch update: Zammad 7.2.2 vendor release and Zammad package LPE advisory.

All articles

Keep exploring

The engineering desk continues across the ecosystem: security research on shipping agents safely, and plugins that put the standards to work.