IBM SECURITY QRADAR EDR · CVE-2026-91869 · Other
FIX → 3.12.27 ✓ verified
IBM QRadar EDR versions 3.12 through 3.12.26 do not properly rate-limit TOTP verification. A remote attacker with a valid account can keep guessing one-time codes and bypass the second-factor security restriction.
first public Nov 13, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running IBM Security QRadar EDR (ReaQta) 3.12 through 3.12.26. An attacker needs a valid account (low privileges) and network access to the login. They can then guess TOTP codes without being rate-limited and bypass the second factor. IBM lists no workaround. Versions 3.12.27 and later are not affected.
Not affected if no-valid-account, outside-affected-range
Who cares authenticated, ibm-qradar-edr, mfa, network, reaqta, totp
3.12.26 are affected; 3.12.27 is fixedIBM 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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
Upgrade to 3.12.27
3.12.27