---
id: CVE-2026-56725
title: Zammad is a web based open source helpdesk/customer support system
summary: >-
  Zammad is a web based open source helpdesk/customer support system. Prior to
  7.0.2, summary An unauthenticated request to POST
  /api/v1/import/otrs/import_check blocks a Zammad request worker for roughly
  two minutes. The import_check and …
severity: high
cvss: 8.7
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'
cwe:
  - CWE-306
  - CWE-400
vendor: zammad
product: zammad
affected:
  - zammad < 7.0.2
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T18:17:26.330'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-56725'
references:
  - url: >-
      https://github.com/zammad/zammad/commit/a04a95b69496306af4c1fbd369a54981122e67c0
    label: security-advisories@github.com
  - url: 'https://github.com/zammad/zammad/releases/tag/7.0.2'
    label: security-advisories@github.com
  - url: 'https://github.com/zammad/zammad/security/advisories/GHSA-45cx-9mrq-mmcj'
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
cvssSource: cna
ingestedAt: '2026-09-25T18:14:20.464Z'
---

## Overview

Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, summary An unauthenticated request to POST /api/v1/import/otrs/import_check blocks a Zammad request worker for roughly two minutes. The import_check and import_status actions are missing the setup_done_response guard that other actions in the same controller carry, so they execute on fully set-up production instances. The action enters a retry loop against a blank OTRS endpoint, sleeping for 30 s + 45 s between attempts. Impact An unauthenticated remote attacker denies service to a production Zammad instance. Each request costs almost nothing and forces ~115 seconds of server-side blocking. A few requests per second saturate the Puma worker pool. The condition persists as long as the traffic continues. No account, valid import configuration, or target knowledge beyond the hostname is needed. CSRF token is trivially obtained from any prior GET response. This issue is fixed in version 7.0.2.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.