CVE-2026-102490: Zammad GmbH Zammad Improper Privilege Management Vulnerability

Published Sep 30, 2026
·
Updated

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.

Other sources

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.

— MITRE

Affected Software

5 affected components
Zammad GmbH Zammad>=1.5.0<=7.1.0-alpha
Zammad GmbH Zammad
All of the following
Zammad Zammad<7.2.2
Any of the following
Docker Docker
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Discontinue use of Zammad if mitigations are unavailable.

Event History

Sep 30, 2026
CVE Published
via MITRE·04:21 PM
Data Sourced
via MITRE·04:21 PM
Description
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeaknessAffected Software
Oct 2, 2026
Kev Listed
via CISA·12:00 AM
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Systems running any affected Zammad version are exposed if a local process or user can operate as the zammad account. The issue allows that local account to escalate privileges to root.

2

Does this require remote access or authentication to Zammad?

The available information describes this as a local privilege-escalation issue. It identifies the local zammad user as the attacker prerequisite and does not state that remote access to the Zammad application alone is sufficient.

3

Are pre-release builds affected?

Yes. The affected range includes Zammad versions from v1.5.0 through v7.1.0-alpha, including the latest alpha.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203