Log in Start free

Actively exploited · Published Sep 30, 2026 · Assigned by DIVD

CVE-2026-102490Local privilege escalation in Zammad v1.5.0 to v7.2.2 installed via DEB or RPM package

High 8.5 Exploited

In plain English

A high-severity privilege mismanagement in Zammad from Zammad GmbH. Attackers are actively exploiting it in the wild (listed by CISA on October 2, 2026). The chance it is exploited in the next 30 days is estimated at 10.9% (higher than 96% of all known vulnerabilities). 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.

Severity (CVSS 4.0)8.5High
Exploit odds (30 days)10.9%top 4.1% of all CVEs
Exploited in the wildYesCISA KEV since Oct 2, 2026
Attack toolingNoneno public tooling known

CISA guidance

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.

Federal agencies must remediate by Oct 5, 2026.

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

Affected products (as reported)

VendorProductVersions
Zammad GmbH Zammad 1.5.0 – before 7.2.2

Weakness: CWE-269 · Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/AU:Y/V:D

References