Quick answers
- Is CVE-2026-84461 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84461 being exploited in the wild.
- How severe is CVE-2026-84461?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- Zammad <= 7.1.1.
- Is there a fix for CVE-2026-84461?
- A patch was published on 2026-08-03: Version 7.1.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84461 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-84461?
- 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
The vulnerability exists in the two-factor authentication initiation endpoint, which performed password validation without triggering Zammad's standard account lockout or rate-limiting protections. An unauthenticated attacker can make unlimited requests over the network to guess passwords, and the response indicates password correctness before two-factor verification occurs. The fix (version 7.1.2) adds proper authentication method validation and enforces rate limiting at the 2FA stage.
Affected products
- Zammad Zammad <= 7.1.1
Timeline
- 2026-08-04: disclosed
- 2026-08-03: patched: Version 7.1.2