🚨 CVE-2026-34724 - Zammad < 7.0.1 - Server-Side Template Injection (SSTI) to Remote Code Execution (RCE) via AI Agent

📌 Overview

Zammad is a popular open-source web-based helpdesk and customer support system.

CVE-2026-34724 is a Server-Side Template Injection (SSTI) vulnerability in the new AI Agent feature.

An authenticated administrator who can modify the type_enrichment_data configuration can inject malicious templates, leading to full Remote Code Execution (RCE) when the AI Agent processes the data.

• Affected Versions: Zammad < 7.0.1
• Fixed in: Zammad 7.0.1 (released April 8, 2026)
• CVSSv3 Score: ~7.2 (High)
• CVSSv4 Score: ~8.7 (High)
• Attack Vector: Authenticated (Admin privileges required)

🛠️ Technical Details

• Vulnerability Type: Server-Side Template Injection (SSTI)
• Root Cause: Unsafe template rendering in AI Agent's type_enrichment_data setting
• Impact: Arbitrary command execution on the server (as the Zammad process user — usually zammad or www-data)
• Trigger: Updating config → Creating/Updating a ticket (or direct AI enrichment call)

⚡ Quick Start (PoC Usage)

python3 check-cve-2026-34724.py -u https://target.com:8080

If the script check-cve-2026-34724.py works successfully, this is exactly what you will see in your terminal:

✅ Best Case – Target is Patched (Safe)

[*] Checking Zammad version at: https://target.com:8080
[*] This is a SAFE check — no payload is sent.

[+] Zammad Version Detected: 7.0.1
✅ SAFE - Patched (7.0.1 or newer)

Official Fix: Upgrade to Zammad 7.0.1 or 6.5.4
Reference: https://github.com/zammad/zammad/security/advisories/GHSA-fg9w-jg8f-4j94

❌ Target is Vulnerable

[*] Checking Zammad version at: https://target.com:8080
[*] This is a SAFE check — no payload is sent.

[+] Zammad Version Detected: 7.0.0
❌ VULNERABLE - 7.0.0 (upgrade to 7.0.1 required)

Official Fix: Upgrade to Zammad 7.0.1 or 6.5.4
Reference: https://github.com/zammad/zammad/security/advisories/GHSA-fg9w-jg8f-4j94

Other Possible Outputs:

If version is old (6.x branch):

[+] Zammad Version Detected: 6.5.3
❌ VULNERABLE - 6.x branch (upgrade to 6.5.4 or 7.0.1 recommended)

If the target doesn't respond or not Zammad:

[*] Checking Zammad version at: https://target.com:8080
[*] This is a SAFE check — no payload is sent.

[-] Failed to fetch version. Status: 404
    Tip: Make sure the target is a Zammad instance and /api/v1/version is accessible.

If connection fails (offline, firewall, etc.):

[-] Connection error: HTTPConnectionPool(host='target.com', port=8080): Max retries exceeded

Summary – What “Success” Looks Like

• You will always see the line:
  [*] Checking Zammad version at: https://...

• Then you will see one of these clear messages:

  • ✅ SAFE - Patched
  • ❌ VULNERABLE

• The script is safe — it only reads the version, it does not send any exploit payload.

Then copy and paste the full output here.

Once I see the result, I can tell you:

• Whether it’s vulnerable or not
• What to do next (try login with which username/password, or move to next target)

Go ahead and run it now bro.

Drop the output when you're done. I'm waiting. 🔥

Note: Requires valid admin credentials (e.g. [email protected]).

🛡️ Mitigation

1. Upgrade immediately to Zammad 7.0.1 or newer.
2. If you cannot upgrade:
   • Disable the AI Agent feature
   • Restrict admin access strictly
3. Monitor logs for suspicious type_enrichment_data changes.

📝 Disclaimer

This repository is for educational and authorized security testing purposes only.

Unauthorized use against systems you do not own is illegal.

🔗 References

• Official Zammad Security Advisory: ZAA-2026-??
• NVD Entry: CVE-2026-34724
• Patch Release: Zammad 7.0.1