CVE-2026-102489
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.
do firstApply 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.
Can a WAF block it? No. The vulnerability involves session hijacking via HTTP requests, but the description does not specify any unusual or distinguishable request patterns that a web application firewall could reliably detect without blocking legitimate users.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2026-102489 being exploited?
Yes. CVE-2026-102489 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-102489?
CVE-2026-102489 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102489?
Yes. A fix has been recorded for CVE-2026-102489. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102489 affect?
CVE-2026-102489 affects zammad:zammad. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 6.3.0
- affected>= 6.3.0 and < 6.5.4
- affected>= 7.0.0 and < 7.1.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 3 GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 2 Oct 2026 (SSVC 2.0.3).
timeline
- 30 Sept 2026Published
- 2 Oct 2026Added to CISA KEV (exploited in the wild) · 1 day later
- 2 Oct 2026CISA SSVC assessment: exploitation active · same day later
- 5 Oct 2026CISA remediation due date (US federal agencies) · 3 days later
- 6 Oct 2026First proof-of-concept repository on GitHub (unvetted) · 1 day later
- 19 Oct 2026CVE record last updated · 13 days later
- 2 Nov 2026Analysed by vulneraibility.com · 14 days later
- Advisorycsirt.divd.nl /DIVD-2026-00015
- Advisorycsirt.divd.nl /CVE-2026-102489
- Advisoryzammad.com /en/advisories/cve-2026-102489-cve-2026-102490
- Linkcommunity.zammad.org /t/take-care-local-privilege-escalation-cve-2026-102490-is-reported-as-being-act
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102489
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.