Skip to content
Server Security Center
KEVcritical9.4Unsupported product

CVE-2026-102489: Zammad GmbH Zammad Session Fixation

Zammad GmbH Zammad · listed in the CISA catalog of actively exploited vulnerabilities since 2026-10-02.

CVSS v4.0 (CVE record)
9.4
critical
EPSS (exploit probability, 30 days)
50%
higher than 98.9% of all CVEs
Added to CISA KEV
2026-10-02
US federal due date 2026-10-05
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-102489 explained

CVE-2026-102489 is a session fixation flaw (CWE-384) in Zammad, server software from Zammad GmbH. It allows session hijacking that leads to remote code execution as the zammad user. CISA lists it as known to be exploited, and the CVE record carries the "Unsupported product" tag.

Impact

An attacker who hijacks a session can execute code remotely as the zammad user. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation at scale requires manual steps per target. CISA lists the vulnerability as known to be exploited. Whether it has been used in ransomware campaigns is unknown.

Who is affected

The CVE record lists Zammad GmbH Zammad on Linux and Docker, versions ≥ 6.3.0, < 6.5.4, as affected. The fix is in 6.5.4. The description also says the bug is present in 7.0.0 to 7.1.2, but is not exploitable there due to changes in the underlying framework. The record is tagged "Unsupported product", so some affected versions may no longer receive vendor support.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Zammad GmbH ZammadLinux, Docker
    Affected
    • ≥ 6.3.0, < 6.5.4
    Fixed in
    • 6.5.4

How to fix it

  • Update to a fixed version: 6.5.4.
  • Vendor advisory: zammad.com/en/advisories/cve-2026-102489-cve-2026-102490
  • The vendor no longer supports the affected versions – replace or retire them; a fix may never come.
  • CISA's deadline for US federal agencies: 2026-10-05 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Upgrade Zammad to 6.5.4 or a later supported release.
  2. If you run an unsupported version, upgrade or replace it instead of waiting for a fix.
  3. Apply the mitigations in the vendor advisory, as CISA's required action directs.
  4. Restrict network access to Zammad and avoid exposing it directly to the internet where possible.
  5. Check Zammad hosts for signs of compromise, including unexpected activity by the zammad user.
  6. Discontinue use if neither a fix nor mitigations are available, per CISA's required action.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-384 Session Fixation

Questions about CVE-2026-102489

Which version fixes CVE-2026-102489?
The CVE record names 6.5.4 as the fixed version for Zammad on Linux and Docker. Affected versions are ≥ 6.3.0, < 6.5.4.
Are versions 7.0.0 to 7.1.2 at risk?
According to the description, the bug is present in those versions but is not exploitable because of changes in the underlying framework.
Is this vulnerability exploited in the wild?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-10-02, with a US federal due date of 2026-10-05. Ransomware use is listed as unknown.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.