CVE-2026-102490 Exploited in the wild
Zammad GmbH Zammad Improper Privilege Management Vulnerability
- Risk score
- 81/100
- CVSS
- 7.8 v3.1
- Exploit chance (30 days)
- 0.5%
- Published
- 30 Sep 2026
- Added to CISA's exploited list
- 2 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 th…
- Affected
- Zammad Gmbh Zammad
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- Exploited in the wild
Story map
At a glance
Zammad Gmbh Zammad: Red, act today. Zammad versions 6.3.0 to 6.5.4 are vulnerable to a session hijack vulnerability that leads to remote code execution as the zammad user. An attacker could exploit this vulnerability to gain remote code execution.
The flaws
- CVE-2026-102490: Zammad GmbH Zammad Improper Privilege Management Vulnerability (CVSS 7.8 · EPSS 1% · exploited)
- CVE-2026-102489: Zammad GmbH Zammad Session Fixation Vulnerability (CVSS 9.8 · EPSS 1% · exploited)
The fix
Fix: Apply mitigations in accordance with vendor instructions
Who is exposed: {'products': ['Zammad'], 'packages': [], 'versions': ['6.3.0 to 6.5.4', '7.0.0 to 7.1.2']}
Where it stands
- Exploited in the wild
- On CISA's exploited list since 2 Oct
- US federal deadline 5 Oct
How it unfolded
- 2 Oct, CISA (official): Added to the Known Exploited Vulnerabilities list (2 of these flaws)
- 5 Oct, Deadline (official): US federal agencies must have patched
Connects to
- Same weakness: Privilege escalation (CWE-269). 156 other warnings in 30 days
Why it is Red
- CVSS 7.8 high
- Exploited in the wild (CISA KEV)
CISA required action
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.
References
Original 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.
Last activity 2 Oct 2026. Patch Forecast updates every hour.