CVE-2026-102490: Zammad Helpdesk Local Privilege Escalation to Root via Backup Scripts
CVE-2026-102490 is a local privilege escalation vulnerability within the backup scripts and sudoers configurations of Zammad helpdesk installations. Although requiring local access, Chinese state-sponsored actor Storm-0940 (Vapor Panda) chained this vulnerability directly with CVE-2026-102489 using the ARTEX multi-agent autonomous framework to escalate from low-privilege service access to root UID 0 in seconds. Zammad urges organizations to upgrade to version 7 or isolate systems immediately. Hermes rates this vector at HTS 98.
HERMES THREAT SCORE & LOCAL PRIVILEGE ESCALATION VECTORS
Target:Zammad Helpdesk System โ Maintenance & Backup Subsystem (/opt/zammad/contrib/backup.sh) CVSS v3.1 rates this flaw at 8.8 (Local) or 9.8 (Chain Context). The Hermes Threat Score assigns 98 (EXTREME) and HASS 96 due to in-the-wild exploitation cataloged by CISA KEV on October 2, 2026, under Binding Operational Directive (BOD) 26-04 with a mandatory remediation deadline of October 5, 2026. As documented in the official Zammad Security Advisory (ZAA-2026-07), CVE-2026-102490 is a local privilege escalation that cannot be exploited remotely on its own without local access. However, in threat modeling and incident response contexts, adversaries achieving initial access via CVE-2026-102489 can immediately chain this flaw: by exploiting insecure sudoers rules executing /opt/zammad/contrib/backup.sh with unquoted PATH expansions and writable temporary directories, attackers execute arbitrary code as UID 0.
CVE-2026-102490: Zammad Helpdesk Local Privilege Escalation to Root via Backup ScriptsVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Zammad Helpdesk & Ticketing documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Vulnerability Anatomy & Root Cause
Section titled โ1. Technical Vulnerability Anatomy & Root CauseโThe vulnerability lies within the default deployment scripts and sudoers configurations provided with Zammad packages across Debian, Ubuntu, and Red Hat distributions. During installation, the package installer registers a sudoers rule in /etc/sudoers.d/zammad:
# Insecure default rule in Zammad < 6.4.1zammad ALL=(ALL) NOPASSWD: /opt/zammad/contrib/backup.shWhen inspecting /opt/zammad/contrib/backup.sh, multiple structural privilege escalation vectors exist:
#!/bin/bash# Excerpt from vulnerable /opt/zammad/contrib/backup.shBACKUP_DIR=${1:-/var/tmp/zammad_backup}CONFIG_FILE="/opt/zammad/config/database.yml"
# Flaw 1: Insecure PATH declaration without secure resetexport PATH="/tmp/bin:$PATH:/usr/local/bin:/usr/bin:/bin"
# Flaw 2: Creation of temporary directories with loose umaskif [ ! -d "$BACKUP_DIR" ]; then mkdir -p -m 777 "$BACKUP_DIR"fi
# Flaw 3: Invocation of system utilities without absolute path specificationsif grep -q "adapter: postgresql" "$CONFIG_FILE"; then echo "Dumping PostgreSQL database..." pg_dump -U zammad -d zammad_production > "$BACKUP_DIR/zammad_db.sql"fi
# Flaw 4: Tar archive compression with untrusted flagstar -czf "$BACKUP_DIR/zammad_files.tar.gz" -C /opt/zammad/storage .Because the shell script executes under root privileges via sudo without secure_path isolation or absolute binary invocations, any user with access to the zammad account can plant a trojaned binary named pg_dump or tar in /tmp/bin/ or manipulate BACKUP_DIR symlinks to overwrite critical system targets such as /etc/shadow or /etc/cron.d/root_job.
2. Affected Versions & Remediation Matrix
Section titled โ2. Affected Versions & Remediation Matrixโ| Release Stream | Affected Versions | Fixed Release | Operational Action |
|---|---|---|---|
| Zammad 6.5 | 6.5.0 | 6.5.1 | Upgrade package; audit /etc/sudoers.d/zammad |
| Zammad 6.4 | 6.4.0 and earlier | 6.4.1 | Upgrade package; replace backup.sh with hardened wrapper |
| Legacy Streams (1.5 - 6.3) | All versions | Migrate to 6.4.1 or 6.5.1 | Sudoers rule present since initial v1.5 release; immediate patch required |
3. Exploit Chaining Threat Model & Vendor Advisory Context
Section titled โ3. Exploit Chaining Threat Model & Vendor Advisory ContextโAccording to the official Zammad Security Advisory ZAA-2026-07, CVE-2026-102490 is strictly a local privilege escalation (LPE) and cannot be exploited across the network without pre-existing local shell access or an interactive session on the host.
However, both CVE-2026-102489 and CVE-2026-102490 were concurrently added to the CISA Known Exploited Vulnerabilities (KEV) catalog under BOD 26-04 due to the severe operational risk of exploit chaining:
[Remote Unauthenticated Adversary] โ โ 1. Inbound Webhook Session Fixation & Object Deserialization (CVE-2026-102489) โผ[Puma Worker Process (uid=1001: zammad)] โ โ 2. Local Environment Inspection โ - Detected: sudo -l -> "NOPASSWD: /opt/zammad/contrib/backup.sh" โ - Placed trojaned binary in writable PATH (e.g., /tmp/bin/pg_dump) โผ[Sudo Invocation: sudo /opt/zammad/contrib/backup.sh] โ โ 3. Root Execution Hijacking (CVE-2026-102490) โ - Unsanitized PATH triggers trojaned binary with effective UID 0 โ - Spawns reverse root shell & establishes persistence โผ[Host Root Compromise (UID 0)]Key considerations for incident responders:
- Local Prerequisite vs Multi-Stage Reality: An unauthenticated remote attacker who discovers an exposed Zammad instance cannot trigger CVE-2026-102490 directly. However, chaining it with CVE-2026-102489 collapses the boundary between unauthenticated external access and full root compromise.
- Remediation Priority: Upgrading to Zammad 7.2.0 (or 6.4.1/6.5.1 on maintenance branches) resolves both vectors, while revoking the
NOPASSWDsudoers entry immediately breaks the privilege escalation stage.
4. Threat Hunting & Forensic Triage
Section titled โ4. Threat Hunting & Forensic TriageโDetection queries and inspection commands for CSIRT teams:
title: Zammad Backup Script Sudoers Privilege Escalationid: 9a41b802-74f2-4e89-9831-d891b0581402status: highdescription: Detects execution of Zammad backup.sh via sudo followed immediately by child processes originating from /tmp or suspicious binary paths.references: - https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-102490 - https://csirt.divd.nl/cases/DIVD-2026-00015/author: Hermes Codex Threat Intelligencedate: 2026-10-03logsource: category: process_creation product: linuxdetection: selection_sudo: Image|endswith: '/sudo' CommandLine|contains: '/opt/zammad/contrib/backup.sh' selection_hijack: Image|startswith: - '/tmp/' - '/var/tmp/' - '/dev/shm/' CommandLine|contains: - 'pg_dump' - 'tar' - 'gzip' condition: selection_sudo or selection_hijacklevel: critical// Azure Sentinel / Defender for Endpoint on Linux// Detect Zammad user executing sudo backup.sh with abnormal child binary invocationsDeviceProcessEvents| where InitiatingProcessAccountName =~ "zammad"| where ProcessCommandLine has "sudo" and ProcessCommandLine has "backup.sh"| project Timestamp, DeviceName, FileName, ProcessCommandLine, InitiatingProcessCommandLine, AccountName| join kind=inner ( DeviceProcessEvents | where InitiatingProcessCommandLine has "backup.sh" | where FolderPath startswith "/tmp" or FolderPath startswith "/var/tmp") on DeviceName| order by Timestamp desc#!/bin/bash# Immediate Root LPE Verification on Zammad Serversecho "=== [1] Checking Sudoers Configuration ==="grep -rn "backup.sh" /etc/sudoers /etc/sudoers.d/ 2>/dev/null
echo "=== [2] Checking Permissions on /opt/zammad/contrib/backup.sh ==="ls -la /opt/zammad/contrib/backup.sh 2>/dev/null
echo "=== [3] Checking for Suspicious Executables in /tmp and /var/tmp ==="find /tmp /var/tmp /dev/shm -type f -perm /111 -exec ls -la {} + 2>/dev/null
echo "=== [4] Inspecting Auditd Logs for Sudo Execution by zammad ==="ausearch -m USER_CMD -ua zammad --raw 2>/dev/null | grep -E "backup\.sh"5. Remediation Strategy & System Hardening
Section titled โ5. Remediation Strategy & System Hardeningโ-
Revoke Unsafe Sudoers Permissions: Remove or comment out the NOPASSWD directive for
backup.shin/etc/sudoers.d/zammad:Terminal window sed -i 's/^zammad ALL=(ALL) NOPASSWD: \/opt\/zammad\/contrib\/backup.sh/# &/' /etc/sudoers.d/zammad -
Apply Zammad 6.4.1 or 6.5.1 Update: Upgrade to the patched Zammad packages where
backup.shenforces strict PATH sanitization (PATH=/usr/bin:/bin) and checks that executable binaries resolve exclusively to root-owned system paths:Terminal window apt-get update && apt-get install --only-upgrade zammad -
Verify File Ownership and Permissions: Ensure that
/opt/zammad/contrib/scripts are strictly owned byroot:rootwith mode0755or0700:Terminal window chown -R root:root /opt/zammad/contrib/chmod 700 /opt/zammad/contrib/backup.sh -
Mount /tmp with noexec: Where feasible in production environments, mount
/tmp,/var/tmp, and/dev/shmwith thenoexec,nosuid,nodevflags to thwart binary staging.