Zammad privilege escalation through writable service files
CVE-2026-102490Known exploitedCritical
Zammad packages built with packager.io (DEB and RPM) ran service processes as root before dropping privileges to the unprivileged zammad account. An attacker with write access as the zammad user could modify files executed during this root phase to escalate to full root privileges. The automatic restart of affected services meant an attacker could exploit this vulnerability within seconds without requiring administrator action. Only packaged installations were affected; source and container image installations were not vulnerable.
Plain English summary of the NVD and CISA text, checked by machine against both.
Scores and dates
- Added to KEV
- 2 Oct
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
Detail
Zammad GmbH Zammad. 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.
Weakness: CWE-269 (opens in a new tab)
Affected versions
- zammad zammad: before 7.2.2