Advisory

CVE-2026-102490: Zammad GmbH Zammad Improper Privilege Management Vulnerability — what to do now

CVE-2026-102490 affects Zammad GmbH Zammad and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog — it is being exploited in the wild, rated HIGH (CVSS 7.8). Here is what it is, who is affected, and the response. No exploit details.

TL;DR: CVE-2026-102490 is a known-exploited vulnerability in Zammad GmbH Zammad. 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. Then confirm no exposed, unpatched instance remains on your perimeter.

What CVE-2026-102490 is

According to the public vulnerability record, 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.

CISA summarises it as: Zammad GmbH Zammad contains an improper privilege management vulnerability that can allow the local zammad user to escalate privileges to root. This vulnerability can be chained with CVE-2026-102489.

Affected product & severity

CVE-2026-102490 affects Zammad GmbH Zammad. Confirm exact affected and fixed versions against the vendor's advisory.

PropertyDetail
CVECVE-2026-102490
VendorZammad GmbH
ProductZammad
CVSS7.8 (HIGH)
VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
WeaknessCWE-269
Added to CISA KEV2026-10-02

Why it is urgent

This CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog (added 2026-10-02) — a list of flaws with confirmed exploitation in the wild. US federal agencies are required to remediate KEV entries on a deadline; for everyone else it is a strong signal to prioritise this now rather than wait. There is no proof-of-concept or exploit detail in this advisory by design.

What to do now

  1. 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 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.
  2. Apply the vendor's patch or mitigation for Zammad GmbH Zammad on every affected instance, per the official advisory linked below.
  3. Inventory every instance — production, staging, legacy and third-party appliances that bundle it. You cannot patch what you have forgotten you run.
  4. Verify the version actually deployed, not the one you think you run; the risk is the build actually serving traffic.
  5. Check for internet exposure. A known-exploited flaw on a reachable instance is an active risk — confirm none is exposed that should not be.

How to confirm your exposure

The hard part of a known-exploited CVE is rarely the patch — it is knowing where a reachable, unpatched instance still exists: a forgotten host, a staging box that drifted public, a third-party appliance. AssurePort's network and host penetration testing discovers exposed services, fingerprints their versions, and correlates them against known-exploited vulnerabilities — so a newly-weaponised CVE is checked against your real external footprint, including the hosts you don't have on a list. That is the window continuous testing is built to close.

Sources & further reading: NVD CVE-2026-102490 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: csirt.divd.nl, csirt.divd.nl, github.com, zammad.com. This advisory contains no exploit code.

Frequently asked questions

What is CVE-2026-102490?

CVE-2026-102490 is a vulnerability in Zammad GmbH Zammad, rated HIGH (CVSS 7.8), listed in the CISA Known Exploited Vulnerabilities catalog. 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.

Is CVE-2026-102490 being exploited?

Yes — it is in the CISA KEV catalog (added 2026-10-02), which lists vulnerabilities with confirmed in-the-wild exploitation. Treat it as an active, prioritise-now risk.

Which products are affected?

Zammad GmbH Zammad. Confirm the exact affected and fixed versions against the vendor's official security advisory before acting.

What should I do right now?

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. Then inventory every instance, verify the version actually deployed, and confirm none is exposed and unpatched on your perimeter.