CVE-2026-102490highunder attackCWE-269

CVE-2026-102490: high-severity vulnerability in Zammad

Local privilege escalation in Zammad v1.5.0 to v7.2.2 installed via DEB or RPM package

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

56Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA.

ssvc Actcvss 8.5epss 11%
from disclosure to weapon
Published on NVDSep 30
CISA KEV+2d
Action required by CISAfederal deadline: 2026-10-05

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.

In short

A security flaw in Zammad versions up to 7.1.0-alpha allows the local zammad user account to gain root (administrator) privileges on the system. This is dangerous because anyone with access to that user account can take complete control of the server.

Technical detail

CWE-269 (Improper Access Control) enables privilege escalation from the unprivileged local zammad user to root. The vulnerability affects all Zammad versions through 7.1.0-alpha; local access to the zammad user account is required as a precondition. Successful exploitation grants full system-level control, representing a critical integrity and confidentiality impact.

Summary generated and translated by AI from the official description.
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.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/AU:Y/V:D
Affected products
Zammad GmbH · Zammad