CVE-2026-91869 in Security QRadar EDR
Summary
by MITRE • 11/14/2026
IBM Security QRadar EDR 3.12 through 3.12.26 could allow a remote authenticated attacker to bypass security restrictions due to improper rate limiting on TOTP verification.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/14/2026
The vulnerability identified in IBM Security QRadar Extended Detection and Response (EDR) versions 3.12 through 3.12.26 represents a critical flaw in the authentication mechanism, specifically concerning the implementation of Time-based One-Time Passwords or TOTP verification protocols. This security deficiency arises from an improper rate limiting configuration within the application logic that handles multi-factor authentication challenges. In standard secure implementations, systems must enforce strict throttling on login attempts to prevent brute-force attacks and credential stuffing campaigns. However, in this specific version range of QRadar EDR, the server fails to adequately restrict the number of TOTP verification requests a user can submit within a given timeframe. This oversight allows an attacker who has already obtained valid credentials through phishing or other means to attempt multiple TOTP codes rapidly without being blocked by the system's security controls.
From a technical perspective, this flaw falls under the category of insufficient anti-automation mechanisms and improper input validation as defined in the Common Weakness Enumeration (CWE) standards. Specifically, it aligns with CWE-307 which describes Improper Restriction of Excessive Authentication Attempts. The absence of effective rate limiting means that the authentication endpoint does not implement exponential backoff or temporary account lockouts after a certain threshold of failed attempts is reached. Consequently, an authenticated attacker can leverage automated scripts to iterate through possible TOTP codes until one matches the current time window. Since TOTP algorithms are deterministic and based on shared secrets and time intervals, the search space for a six-digit code is relatively small, making brute-force attacks feasible if rate limits are not enforced at the server level.
The operational impact of this vulnerability is severe as it effectively neutralizes the protective benefits provided by multi-factor authentication. While QRadar EDR requires users to provide both something they know (password) and something they have (the TOTP code), the lack of rate limiting on the second factor allows an adversary to bypass the MFA requirement entirely after compromising the password. This leads directly to unauthorized access to the management console, which could result in a complete compromise of the security infrastructure managed by QRadar EDR. An attacker with administrative privileges can alter logging configurations, disable detection rules, exfiltrate sensitive data collected from endpoints, or deploy further malicious tools within the network environment.
This vulnerability maps closely to techniques observed in real-world threat actor campaigns as documented in the MITRE ATT&CK framework. It facilitates the Initial Access and Credential Access tactics by allowing attackers to bypass MFA protections using brute-force methods against authentication tokens. The ability to automate TOTP guessing significantly lowers the barrier for entry, enabling less sophisticated adversaries to gain access to high-value targets that rely on QRadar EDR for their security operations center functions.
To mitigate this risk, organizations running affected versions of IBM Security QRadar EDR must apply the latest available patches or updates provided by IBM immediately. These updates include fixes that enforce stricter rate limiting policies on TOTP verification endpoints, ensuring that repeated failed attempts trigger appropriate countermeasures such as temporary account locks or CAPTCHA challenges. In addition to patching, administrators should review access logs for any signs of unusual authentication patterns prior to the update, such as a high volume of login failures from specific IP addresses or user accounts. Implementing network-level rate limiting via firewalls or web application firewalls can also provide an additional layer of defense by throttling requests to the authentication service before they reach the vulnerable application logic.