CriticalCVE-2026-102489

    Undisclosed RCE in Zammad v6.3 and higher (CVE-2026-102489)

    Published Last modified In CISA KEV since Sources: pwn.watch, CVE.org, BSI

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. Update Zammad to version 6.5.4. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Zammad lt 6.3.0..6.5.4
    Fixed in
    • Zammad 6.5.4

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: pwn.watch, CVE.org, BSI

    22.5 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 97.7

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    255.36 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.7
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    22.5 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    97.7
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 2 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-384

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is reachable over the network without authentication or user interaction. Chained with CVE-2026-102490, it gives attackers code execution on the helpdesk server, with full impact on confidentiality, integrity and availability. Statistical exploitation likelihood is currently only moderate and CISA has not flagged ransomware use, but KEV listing confirms real-world attacks. Helpdesk platforms also concentrate customer PII, mailbox credentials and integration secrets, which makes them an attractive foothold for data theft and lateral movement. Treat internet-facing 6.x instances as top priority, including a compromise assessment and a review of potential NIS2 and GDPR notification duties. Internal-only instances and 7.0.0–7.1.2 deployments can move to 7.2 in a prompt but regular patch cycle.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory every exposed Zammad instance and check its version. Versions 6.3.0 through 6.5.4 are affected. The bug is also present in 7.0.0 through 7.1.2, but the vendor states it is not exploitable there due to framework changes. Check the version via Admin → System → Info or with dpkg -l zammad / rpm -q zammad.
      • Upgrade to Zammad 7.2. The context lists this version as patched. For the 6.x branch, the context contradicts itself by listing 6.5.4 as both affected and fixed. Look up the fixed 6.x version in the vendor advisory and treat 6.5.4 as vulnerable until that is confirmed.
      • Cut internet exposure now if you cannot patch immediately. Restrict the reverse proxy (nginx/Apache in front of Puma on 127.0.0.1:3000 and the WebSocket on 6042) to VPN, corporate ranges or an IP allowlist. Put customer portals into maintenance mode if necessary.
      • Invalidate all existing sessions. Session fixation means pre-planted or hijacked sessions remain valid after patching. Purge active sessions, for example via zammad run rails c and the session table; confirm the exact procedure in vendor documentation. Consider rotating secret_key_base as well.
      • Rotate credentials: passwords and API tokens for admin and agent accounts, email channel credentials (IMAP/SMTP/Microsoft 365/Google OAuth), and integration secrets (LDAP bind, webhooks, Elasticsearch, telephony). Code execution as zammad means /opt/zammad/config and the database credentials should be considered exposed.
      • Assess and patch CVE-2026-102490 in parallel. Chaining the two vulnerabilities is the likely attack path.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place the Zammad application server in a DMZ or application zone. Allow egress only to required destinations (mail server, Elasticsearch, PostgreSQL, package repository). Block generic outbound HTTP/HTTPS and external DNS to hamper reverse shells and payload staging.
      • WAF/reverse proxy: Reject session cookies (_zammad_session_*) supplied via query strings or URL parameters, and block requests that carry session IDs in GET parameters. Rate-limit /api/v1/signin, /api/v1/signshow and /api/v1/sessions. Enforce Secure, HttpOnly and SameSite=Strict cookie attributes at the proxy if they are missing.
      • Endpoint hardening: Run the zammad service account with no login shell and no sudo rights. Remove runtime write access to /opt/zammad/app and /opt/zammad/config where the packaging allows it. Optionally use AppArmor/SELinux to stop Puma/Ruby from spawning sh, bash, curl, wget, nc or python.
      • IAM/least privilege: Reduce admin roles to the minimum. Enforce 2FA for all agents and admins. Restrict the admin interface to management networks via a proxy rule.
      • Configuration: Temporarily disable unneeded authentication paths (third-party login, customer self-registration) to shrink the session-handling attack surface.
    3. Runbook step 3

      Detection rules

      • Process ancestry (EDR, Sysmon for Linux EID 1, auditd execve): a shell or network tool spawned by Ruby/Puma under uid=zammad. Sigma shape: ParentImage|endswith: ['/ruby','/puma'] AND Image|endswith: ['/sh','/bash','/curl','/wget','/nc','/python3'] AND User: zammad. auditd rule: -a always,exit -F arch=b64 -S execve -F uid=$(id -u zammad) -k zammad_exec.
      • Web server access logs: the same session ID appearing from different source IPs or user agents within a short window, plus session parameters in URLs. SPL sketch: index=web sourcetype=nginx host=zammad* | rex "_zammad_session_\w+=(?<sid>[^;]+)" | stats dc(clientip) as ips values(clientip) by sid | where ips>1.
      • Zammad application data: unexpected new admin accounts, role changes, new API tokens, altered triggers, macros or webhooks, and modified email channels since 6.3.0 was deployed. Review Admin → Monitoring, the history table and /opt/zammad/log/production.log.
      • Network telemetry (Zeek/Suricata): outbound connections from the Zammad host to unfamiliar destinations, especially long-lived TCP sessions on unusual ports or HTTP downloads of ELF binaries and scripts (conn.log, and http.log with mime_type application/x-executable or text/x-shellscript).
      • File integrity (auditd/FIM): new or modified files owned by zammad under /opt/zammad, /tmp and /var/tmp, plus crontab entries or ~/.ssh/authorized_keys for the zammad user.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: pwn.watch, cvelistv5, NVD (NIST), CISA KEV Catalog, BSI WID Portal, BSI CSAF

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Zammad GmbHZammad
    • 6.3.0 – < 6.5.4
    • 6.5.4
    zammadzammad
    • 6.3.0 – ≤ 6.5.4
    • —
    ZammadZammad
    • < 7.2
    • 7.2

    Vendors and products

    Weakness classes (CWE)

    • CWE-384Session Fixation

      Compound

      Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.

      Entry at MITRE CWE-384

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    PoC-in-GitHub (nomi-sec)CVE-2026-102489 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-102489 (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • csirt.divd.nlDIVD-2026-00015Third-party advisory
    • csirt.divd.nlCVE-2026-102489Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-1024…government-resource
    • zammad.comen/advisories/cve-2026-102489-cve-2026-102490Vendor advisory
    • community.zammad.orgt/take-care-local-privilege-escalation-cve-2026-102490-is-repor…Technical description
    • pwn.watchpwn.watch: Zammad GmbH Zammad: Zammad GmbH Zammad Improper Privilege Management Vulnerabilitypwn-watch
    • zammad.comZammad GmbH Zammad — CVE-2026-102490pwn-watch
    • NVD (NIST)NVD: CVE-2026-102490pwn-watch
    • NVD (NIST)NVD: CVE-2026-102489pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentremoved
      {"id":"CVE-2026-102489","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-09T15:59:10.993019Z"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2026-102489","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-02T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentremoved
      {"id":"CVE-2026-102489","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-02T00:00:00+00:00"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2026-102489","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-09T15:59:10.993019Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. NVD analysis modifiedNVD

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationchanged
      AND OR *cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 6.5.4 *cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:* versions from (including) 7.0.0 up to (including) 7.1.3 OR cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* cpe:2.3:a:docker:docker:-:*:*:*:*:*:*:*
      AND OR *cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (including) 6.5.4 OR cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* cpe:2.3:a:docker:docker:-:*:*:*:*:*:*:*
      Reference typeadded
      —
      Dutch Institute for Vulnerability Disclosure: https://community.zammad.org/t/take-care-local-privilege-escalation-cve-2026-102490-is-reported-as-being-actively-exploited/21297/2 Types: Vendor Advisory
      Reference typeadded
      —
      Dutch Institute for Vulnerability Disclosure: https://zammad.com/en/advisories/cve-2026-102489-cve-2026-102490 Types: Vendor Advisory

      Source identifier: nvd@nist.gov

    4. Record modifieddivd.nl

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Tagadded
      —
      unsupported-when-assigned
      Descriptionchanged
      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 vulnerability is also present in version 7.0.0 to version 7.1.3, but not exploitable due to environment conditions.
      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.
      Affected versions (publisher)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/102xxx/CVE-2026-102489.json">CVE-2026-102489</a>
      Referenceadded
      —
      https://community.zammad.org/t/take-care-local-privilege-escalation-cve-2026-102490-is-reported-as-being-actively-exploited/21297/2
      Referenceadded
      —
      https://zammad.com/en/advisories/cve-2026-102489-cve-2026-102490

      Source identifier: csirt@divd.nl

    5. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentremoved
      {"id":"CVE-2026-102489","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-02T16:27:26.039890Z"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2026-102489","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-02T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Show 5 older changes
    1. NVD analysis modifiedNVD

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Reference typeadded
      —
      CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102489 Types: US Government Resource

      Source identifier: nvd@nist.gov

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Weakness type: CWE-384

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Weakness type (CWE)added
      —
      CWE-384
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102489
      SSVC assessmentadded
      —
      {"id":"CVE-2026-102489","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-02T16:27:26.039890Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Initial analysis by NVDNVD

      Newly listed as affected:
      • Zammad (6.3.0 – before 6.5.4; 7.0.0 – through 7.1.3)

      CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

      Weakness type: CWE-384

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
      Weakness type (CWE)added
      —
      CWE-384
      Product configurationadded
      —
      AND OR *cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 6.5.4 *cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:* versions from (including) 7.0.0 up to (including) 7.1.3 OR cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* cpe:2.3:a:docker:docker:-:*:*:*:*:*:*:*
      Reference typeadded
      —
      Dutch Institute for Vulnerability Disclosure: https://csirt.divd.nl/CVE-2026-102489 Types: Third Party Advisory
      Reference typeadded
      —
      Dutch Institute for Vulnerability Disclosure: https://csirt.divd.nl/DIVD-2026-00015 Types: Third Party Advisory

      Source identifier: nvd@nist.gov

    4. CISA KEV entry updated9119a7d8…

      4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Date Addedadded
      —
      2026-10-02
      Due Dateadded
      —
      2026-10-02
      Required Actionadded
      —
      2026-10-02
      Vulnerability Nameadded
      —
      2026-10-02

      Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

    5. Receiveddivd.nl

      CVSS V4.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

      Description added or changed

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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 vulnerability is also present in version 7.0.0 to version 7.1.3, but not exploitable due to environment conditions.
      CVSSadded
      —
      AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:C/RE:X/U:X
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/102xxx/CVE-2026-102489.json">CVE-2026-102489</a>
      Referenceadded
      —
      https://csirt.divd.nl/CVE-2026-102489
      Referenceadded
      —
      https://csirt.divd.nl/DIVD-2026-00015

      Source identifier: csirt@divd.nl

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-102489
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-102489"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-102489.svg?lang=en" alt="CVE-2026-102489 – NEOSEC Intel" height="20"></a>