Skip to content
PiLabs security advisory Updated 2 November 2026
High 7.8 CVE-2026-102490 Known exploited

Local privilege escalation to root in Zammad DEB and RPM packages

Affected
Zammad GmbH Zammad
Affected versions
< 7.2.2
Disclosed
Last updated
CVSS 3.1 vector
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Written automatically on 27 October 2026 from the NVD and the CISA catalogue of known exploited vulnerabilities. The facts above come from those sources; check them before you act. Updated by Pinet on 2 November 2026. Sources of this advisory

Zammad GmbH reports that DEB and RPM packages of Zammad let a local attacker with write access as the zammad service account gain root. CISA lists the flaw as exploited.

What is affected

Zammad GmbH reports that Zammad packages built with packager.io, in DEB and RPM format, are affected by CVE-2026-102490. The sources give the affected version range as < 7.2.2, which means the versions before 7.2.2. According to the description, installations from source and the official container images are not affected.

The weakness is classed as CWE-269, improper privilege management. The CVSS 3.1 base score is 7.8, which is high severity. The scoring describes a local attack with low complexity, low privileges required and no user interaction.

What the flaw allows

The sources describe a local privilege escalation. An attacker who already has file system write privileges as the unprivileged zammad service account could gain full root privileges on the host.

The cause, as described, is that service processes began running as root and executed files that were owned by, and writable by, the zammad account. Only after that did they drop their identity to that account. Because the affected services were restarted automatically whenever they stopped, the sources say an attacker with that foothold could have escalated within seconds, and no administrator interaction was required.

The flaw does not give an attacker the first foothold. It matters once someone can already write files as the zammad account, and in that case it turns a limited compromise into a full compromise of the host.

Exploitation

CISA lists this vulnerability as exploited in its Known Exploited Vulnerabilities catalogue and added it on 2026-10-02. CISA's stated deadline for US federal agencies to act is 2026-10-05. CISA lists the use in ransomware campaigns as unknown. The vulnerability was disclosed on 2026-09-30.

Pinet has not analysed or tested this vulnerability. The information here comes from the public sources linked below.

What to do

First establish whether your Zammad installation comes from the DEB or RPM packages. If it does, compare your installed version with the affected range < 7.2.2. The Zammad security advisory lists the fixed releases and explains how to check your exposure.

CISA's required action is to apply mitigations in accordance with the vendor's instructions. The CISA Known Exploited Vulnerabilities catalogue and the NVD entry for CVE-2026-102490 give further detail.

What to do

Follow the instructions in the Zammad security advisory, which lists the fixed releases for the DEB and RPM packages. CISA's required action is to apply mitigations in accordance with vendor instructions. Installations from source and the official container images are not affected, according to the description. The Zammad release notes give further information on releases.

Sources

Mentioned in security bulletins

All vulnerabilities

Need to know whether these vulnerabilities affect you?

A consultant can check which of the affected products you run and what to fix first. For a wider review, ask for a security assessment.