Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-84461 Overview
Zammad is a web-based open source helpdesk and customer support system. A vulnerability in Zammad versions prior to 7.1.2 allows attackers to brute-force user passwords through the two-factor authentication (2FA) initiation endpoint. The endpoint failed to enforce Zammad's normal account lockout and rate-limiting controls when verifying credentials. The server response also distinguished between correct and incorrect passwords before the second authentication factor was evaluated. This exposes an observable information discrepancy that attackers can use to validate guessed credentials against any account. The issue is tracked under [CWE-203: Observable Discrepancy] and is resolved in version 7.1.2.
Critical Impact
Attackers can perform unlimited password guessing against any Zammad account without triggering lockouts, enabling brute-force of weak or reused passwords despite 2FA being enabled.
Affected Products
- Zammad (open source helpdesk and customer support system)
- All versions prior to 7.1.2
- Deployments exposing the 2FA initiation REST and GraphQL endpoints
Discovery Timeline
- 2026-09-25 - CVE-2026-84461 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-84461
Vulnerability Analysis
The flaw resides in the Zammad 2FA initiation flow exposed through both the REST sessions controller and the GraphQL TwoFactorMethodInitiateAuthentication mutation. When a user submitted a username and password alongside a selected 2FA method, the controller validated the password first and returned a distinct error only when credentials were invalid. A separate error message was returned when the password was correct but the requested 2FA method was unavailable. This behavioral difference acts as a credential oracle. The endpoint also bypassed the authentication throttling applied to the standard login path, which meant brute-force protections such as temporary account lockout and rate limiting were not triggered.
Root Cause
Two defects combine to create the issue. First, the 2FA initiation endpoints did not apply the throttling middleware used elsewhere for authentication. Second, the control flow emitted a different exception (The two-factor authentication method is not enabled.) when password verification succeeded but the 2FA method check failed, versus the generic credential error on password failure. This observable discrepancy [CWE-203] lets an attacker infer password correctness independently of 2FA state.
Attack Vector
Exploitation requires only network access to the Zammad web interface. An unauthenticated attacker iterates candidate passwords for a known username against the 2FA initiation endpoint. Because no throttling applies and the response differs based on password validity, the attacker can enumerate correct credentials for accounts protected by weak or reused passwords. The second authentication factor remains a barrier to full login, but credential exposure enables credential-stuffing campaigns and further attack chaining.
# Patch: app/controllers/sessions_controller.rb
# Collapses password validation and 2FA method lookup into a single
# error path, and adds throttling via a shared concern in GraphQL.
auth = Auth.new(params[:username], params[:password], only_verify_password: true)
begin
auth.valid!
two_factor_method = auth.user.auth_two_factor.authentication_method_object(params[:method])
raise Auth::Error::AuthenticationFailed if !two_factor_method&.enabled? || !two_factor_method&.available?
rescue Auth::Error::AuthenticationFailed
raise Exceptions::UnprocessableContent, __('The username or password is incorrect.')
rescue => e
logger.error(e)
raise Exceptions::UnprocessableContent, __('The username or password is incorrect.')
end
render json: two_factor_method.initiate_authentication, status: :ok
Source: Zammad commit d51254f1
The GraphQL mutation receives the same hardening by including the Gql::Concerns::HandlesThrottling module:
# app/graphql/gql/mutations/two_factor_method_initiate_authentication.rb
module Gql::Mutations
class TwoFactorMethodInitiateAuthentication < BaseMutation
include Gql::Concerns::HandlesThrottling
description 'Fetches the initiation phase data for a two-factor authentication method.'
argument :login, String, description: 'User name'
Source: Zammad commit d51254f1
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-84461
Indicators of Compromise
- High volume of POST requests to the Zammad 2FA initiation REST endpoint under /api/v1/users/two_factor or equivalent session routes from a single source IP
- Repeated GraphQL mutations invoking twoFactorMethodInitiateAuthentication with varying password arguments for the same login value
- Elevated rates of UnprocessableContent responses in Zammad application logs without corresponding account lockout events
Detection Strategies
- Baseline typical request rates to 2FA initiation endpoints and alert on statistical anomalies per source IP and per target username
- Correlate failed authentication attempts across REST and GraphQL interfaces to identify distributed brute-force patterns
- Hunt for successful logins immediately following bursts of 2FA initiation requests against the same account, which may indicate credential validation prior to full compromise
Monitoring Recommendations
- Forward Zammad Rails application logs and web server access logs to a centralized logging platform for correlation
- Enable alerting on authentication-related endpoints with thresholds tuned per user and per source address
- Monitor for user-agent and source IP clustering that indicates automated brute-force tooling
How to Mitigate CVE-2026-84461
Immediate Actions Required
- Upgrade all Zammad instances to version 7.1.2 or later without delay
- Review authentication logs for anomalous access patterns against the 2FA initiation endpoints prior to patching
- Force password resets for accounts that may use weak or reused credentials, particularly privileged administrator accounts
- Verify that any WAF or reverse proxy in front of Zammad applies rate limiting to all authentication paths
Patch Information
The fix is delivered in Zammad 7.1.2 via commit d51254f1c6da13f6ee27636a5c82e53f7e59666b. The patch unifies password and 2FA method validation into a single error path, so the response no longer distinguishes between invalid passwords and unavailable 2FA methods. The GraphQL mutation includes the HandlesThrottling concern to enforce rate limiting consistent with other authentication flows. See the GitHub Security Advisory GHSA-6vh5-pfp2-5rmh for upstream guidance.
Workarounds
- Restrict access to the Zammad web interface to trusted networks or VPN until the patch is applied
- Deploy a reverse proxy rule to rate-limit requests to the 2FA initiation endpoints by source IP and username
- Enforce strong, unique password policies and rotate credentials for accounts handling sensitive support queues
# Example nginx rate-limit configuration for the 2FA initiation path
http {
limit_req_zone $binary_remote_addr zone=zammad_2fa:10m rate=5r/m;
server {
location ~ ^/api/v1/.*two_factor {
limit_req zone=zammad_2fa burst=5 nodelay;
proxy_pass http://zammad_backend;
}
location /graphql {
limit_req zone=zammad_2fa burst=5 nodelay;
proxy_pass http://zammad_backend;
}
}
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

