Skip to content
NewA calmer, faster ZeroHour
VulnerabilityKEV9 · 1 read

CVE-2026-102490

Local privilege escalation to root in all Zammad versions

CISA: Zammad GmbH Zammad Improper Privilege Management Vulnerability

CVSS 4.0
9.4 critical
EPSS
11%p96
Published
·
Added to KEV
Analyze CVE-2026-102490 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

All versions of the Zammad helpdesk, including the latest alpha, let the local zammad system user escalate privileges to root. The flaw is a local privilege escalation on hosts where that account exists; the advisory does not describe a separate unauthenticated remote code-execution bug. A successful escalation gives full root control of the Zammad server, including tickets, credentials, and the underlying operating system. Every Zammad installation is in scope because no unaffected version is identified. CVSS 4.0 scores it 9.4 critical with exploit maturity Attacked (E:A); it is not listed in CISA KEV and no public proof-of-concept is known.

What to do: Treat every Zammad host as vulnerable: no fixed release is named in the advisory, and all versions including the latest alpha are affected. Restrict login and sudo/polkit rights for the local zammad system account, review that account for unexpected privileges, and apply a vendor or DIVD patch as soon as one is published. Watch the host for unexpected root processes owned by or spawned from the zammad user.

ProductAffected
Zammad GmbH ZammadAll versions, including the latest alpha
Estimated exposure
moderateOn the order of 1,000–10,000 self-hosted Zammad servers — Zammad is a widely used self-hosted open-source helpdesk, mainly in organizations rather than by consumers; the advisory gives no install count or internet-scan total, so this is an order-of-magnitude estimate of server installations, not…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

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. Only installations from the DEB and RPM packages were affected — installations from source or the official container images were not. All released packaged versions were affected.

KEVCISA Known Exploited Vulnerability
Affected
Zammad GmbH Zammad
Required action
Apply 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.
Due date
Ransomware use
Unknown
Vendors
zammad
Products
zammad
Weakness
CWE-269
Vector
CVSS:4.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/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

In the news

19 stories