dbcve.org
ZammadApplication

CVE-2026-34724

HIGH · 7.2 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1, a server-side template injection vulnerability which leads to RCE via AI Agent exists. Impact is limited to environments where an attacker can control or influence type_enrichment_data (typically high-privilege administrative configuration). This vulnerability is fixed in 7.0.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Server-side template injection (SSTI) vulnerability in Zammad's AI Agent functionality allows remote code execution through manipulation of type_enrichment_data. This requires high-privilege administrative access to the helpdesk system.

MitigationUpgrade Zammad to version 7.0.1 or later to patch the SSTI vulnerability. Restrict administrative access to type_enrichment_data configurations until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZammadApplication
Affected:= 7.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Zammad version
    Run 'zammad --version' or check the application's about page to determine the exact version number
    Affected if The installed version is exactly 7.0.0
  2. Verify AI Agent feature is enabled
    Check Zammad's system configuration for the AI Agent or AI integration settings. Look for enabled status of any AI-related features.
    Affected if AI Agent feature is enabled and configured in the system
  3. Confirm administrative access exposure
    Review which user accounts have administrative privileges, particularly those with access to system configuration or AI feature settings
    Affected if Multiple admin accounts exist or unauthorized admin accounts have been created
  4. Inspect AI Agent configuration for type_enrichment_data
    Check the AI Agent configuration parameters for the type_enrichment_data setting. Look for any unexpected or suspicious values that may indicate injection attempts.
    Affected if The type_enrichment_data parameter contains unexpected template syntax or encoded content

A system is affected if it runs Zammad version 7.0.0 with the AI Agent feature enabled and administrative access is available to manipulate the type_enrichment_data parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Zammad to version 7.0.1 or later to patch the SSTI vulnerability. Restrict administrative access to type_enrichment_data configurations until the patch is applied.

Recommended fix High confidence

7.0.1

  1. 1. Create a complete backup of the Zammad database and configuration files before attempting any upgrade
  2. 2. Upgrade Zammad from version 7.0.0 to version 7.0.1 by following the official upgrade documentation for your deployment method (package-based or source)
  3. 3. After upgrading, restart all Zammad services to ensure the patched code is loaded
  4. 4. Verify the upgrade was successful by checking the Zammad version in the web interface or via command line
  5. 5. Review the type_enrichment_data configuration in the AI Agent settings to ensure no unauthorized changes were made during the vulnerability window

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zammad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34724 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data