CVE-2026-61525 zammad CVE debrief

Who should care

Defenders responsible for Zammad instances, especially those with low-privilege authenticated sessions, should assess exposure and prioritize patching or mitigation. This includes reviewing compensating controls, monitoring for suspicious activity, and verifying affected scope and vendor guidance. Defenders should also track exceptions, retest remediated assets, and close the item only after evidence is documented.

Why it matters

CVE-2026-61525 is a high-severity vulnerability in Zammad that allows authenticated attackers to delete arbitrary files and directories. Defenders should prioritize patching or mitigating this vulnerability, especially in low-privilege authenticated sessions.

• Authenticated attackers can delete arbitrary files and directories
• Low-privilege sessions can be exploited
• Fixes are available in versions 7.0.3 and 7.1.1

Technical summary

The vulnerability is caused by insufficient validation of client-supplied session identifiers, which can be manipulated to reference locations outside the intended storage directory. This leads to the deletion of arbitrary files and directories on the server. The issue is fixed in versions 7.0.3 and 7.1.1. Defenders should prioritize patching or mitigating this vulnerability, especially in low-privilege authenticated sessions. The vulnerability has a high severity score and requires immediate attention from defenders responsible for Zammad instances.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability, especially in low-privilege authenticated sessions.

Recommended defensive actions

• Patch Zammad to version 7.0.3 or 7.1.1
• Verify and restrict access to session management functionality
• Monitor for suspicious file deletion activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in Zammad versions 7.0.2 and 7.1.0, with fixes available in versions 7.0.3 and 7.1.1. Instances using the Redis-based session store are not affected. Evidence is based on official CVE Program and NIST NVD records, as well as source references from [email protected]. Defenders should verify affected scope and vendor guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.