Quick answers
- Is CVE-2026-61525 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61525 being exploited in the wild.
- How severe is CVE-2026-61525?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- Zammad 7.0.2 and 7.1.0.
- Is there a fix for CVE-2026-61525?
- A patch was published on 2026-06-22: Fix committed; versions 7.0.3 and 7.1.1 contain the patch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61525 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-61525?
- Check whether you run Zammad at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in Zammad's session management for websocket and long-polling connections. The application insufficiently validates session identifiers supplied by the client before using them to construct file paths in the session store. An authenticated attacker can manipulate the client_id parameter with path traversal sequences (e.g., "../") to reference files outside the intended session storage directory and delete them. The fix introduces a valid_client_id? validation function to sanitize identifiers before use.
Affected products
- Zammad Zammad 7.0.2 and 7.1.0
Timeline
- 2026-09-25: disclosed
- 2026-06-22: patched: Fix committed; versions 7.0.3 and 7.1.1 contain the patch