inferwire
/
Cybersecurity·2 min read

Zammad Package Flaw Lets Attackers Escalate to Root, CISA Warns

CVE-2026-102490 in Zammad's DEB and RPM packages let a local attacker with the zammad account's file access escalate to root within seconds. CISA lists it as exploited.

TL;DR

  • CVE-2026-102490 in the Zammad help desk's DEB and RPM packages let an attacker who could already write files as the zammad service account become root [^1].
  • CISA added it to its Known Exploited Vulnerabilities catalog on October 2; installations from source or the official container images were not affected [^1].

Background

Zammad is open-source help desk and ticketing software. Privilege escalation flaws turn a limited foothold into full control of a machine, which is why they are often chained with other bugs. CISA's Known Exploited Vulnerabilities (KEV) catalog lists flaws with confirmed exploitation in the wild and sets deadlines for US federal agencies [^1].

What happened

According to NVD, in Zammad packages built with packager.io, service processes started as root and executed files that were owned and writable by the zammad account before dropping to that account's identity [^1]. An attacker who already had write access to the file system as the unprivileged zammad account could therefore get code run as root. Because the affected services restarted automatically whenever they stopped, the escalation could happen within seconds, with no administrator interaction [^1]. All released packaged versions were affected, but only installations from the DEB and RPM packages [^1].

The flaw (CWE-269, improper privilege management) scores 9.4 under CVSS 4.0 and 7.8 under CVSS 3.1 [^1]. NVD published it on September 30, and CISA listed it as exploited on October 2, with a federal deadline of October 5 [^1].

Why it matters

The bug sits in packaging, not in Zammad's application code, which is why source and container installs were safe. It is a reminder that how software is installed and started can matter as much as the code itself: a root process that runs files a lower-privileged account can modify hands that account the keys.

Practical example

Say a company runs Zammad from the official DEB package and an attacker has found a way to write files as the zammad user, for example through a separate bug. With the affected packages, the attacker could replace a file the root-started service runs, wait seconds for a restart, and take over the server [^1]. Updating the package removes that path; installs from the container images never had it [^1].

Related gear

We recommend this book because it provides an excellent foundation in Linux file permissions and system administration, helping you understand how local privilege escalation attacks succeed.

AdvertisementAmazon

Linux Basics for Hackers: Getting Started with Networking, Scripting, and Security in Kali

Sources

  1. [1]NVD — CVE-2026-102490