Vulnerability in Zammad (CVE-2026-34720)
Summary
Vulnerability in Zammad (CVE-2026-34720). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7.0.1 or later.
Original description
The description as published by the source.
Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, the SSO mechanism in Zammad was not verifying the header originates from a trusted SSO proxy/gateway before applying further actions on it. This vulnerability is fixed in 7.0.1 and 6.5.4.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-34720 has been found in Zammad.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade Zammad to 7.0.1 or later.
If unsure, ask your IT team or search "Zammad CVE-2026-34720" on the vendor's site.
CVE-2026-34720 (Zammad) — CWE-346 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 7.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-346) exists in Zammad.
Check the vendor advisory for the affected versions of Zammad.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 7.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Zammad' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Zammad' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Zammadを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Zammad to 7.0.1ステージング環境で 7.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。