Zammad GmbH Zammad: privilege escalation flaw under attack

What is affected

Zammad GmbH Zammad is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

Zammad GmbH Zammad contains an improper privilege management vulnerability that can allow the local zammad user to escalate privileges to root. This vulnerability can be chained with CVE-2026-102489.

What an attacker can do

This is a privilege escalation flaw. It lets an attacker turn limited access into full administrator control. Attackers pair it with another flaw or a malicious file: once anything of theirs runs on the device, this bug lets it take over completely.

How it is reached

Over the internet or network

Access the attacker needs

No account needed

Does the victim have to do something?

Yes, ordinary use is enough

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer Zammad GmbH Zammad at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

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.

Vendor advisories and fixes

• zammad.comzammad.com/en/product/releases/
• community.zammad.orgcommunity.zammad.org/t/take-care-local-privilege-escalation-cve-2026-102490-is-reported-as

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on October 2, 2026, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by October 5, 2026, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 0.6% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 46% of all scored vulnerabilities.

Its CVSS severity score is 9.4 out of 10 (critical), as recorded in the US National Vulnerability Database.

Technical 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.