CVE
IBM Security QRadar EDR rate limit bypass in TOTP verification
- Exploited
- No known exploitation
- Fix
- Fixed in 3.12.27
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is IBM Security QRadar EDR versions 3.12 through 3.12.26. The weakness is in TOTP verification, which has improper rate limiting.
Summary
IBM Security QRadar EDR is affected by a flaw in its TOTP verification, where improper rate limiting lets an attacker bypass security restrictions. An attacker who already has a valid login can exploit this remotely over the network.
Original description
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.
Who should check
Teams running IBM Security QRadar EDR 3.12 through 3.12.26 and their operators or subscriptions that control upgrades.
“IBM Security QRadar EDR 3.12 - 3.12.26”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected product is IBM Security QRadar EDR versions 3.12 through 3.12.26. The weakness is in TOTP verification, which has improper rate limiting.Upgrade to a fixed version: 3.12.27.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-91869 (IBM Security QRadar EDR Improper Restriction of Excessive Authentication Attempts), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-91869 (entry last updated 2026-11-16):
Affected:
- IBM Security QRadar EDR: from 3.12.0, through 3.12.26
Fixed versions: 3.12.27.
Conditions (all must be true for the bug to be hit):
- Affected product is IBM Security QRadar EDR versions 3.12 through 3.12.26. (source: https://www.ibm.com/support/pages/node/7296309)
- The weakness is in TOTP verification, which has improper rate limiting. (source: https://www.ibm.com/support/pages/node/7296309)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-91869 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-91869 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.ibm.com/support/pages/node/7296309
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-91869
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-91869"}.Public exploit activity
- EPSS: 0.32%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Timeline
- CVE published
- First seen by cve.now3 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- IBM Security QRadar EDR
From 3.12.0 · through 3.12.26
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Patch | ibm.com · support/pages/node/7296309 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-91869 |
| Record | NVD · CVE-2026-91869 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-91869
Is CVE-2026-91869 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The TOTP (time-based one-time code) check in IBM Security QRadar EDR does not limit how often login codes can be tried. A signed-in remote user could use that gap to get past a security restriction.Source: ibm.com
Which versions are affected by CVE-2026-91869?
Security QRadar EDR: from 3.12.0 through 3.12.26.Source: cve.now feed data
Am I affected, and how do I check?
IBM Security QRadar EDR versions 3.12 through 3.12.26 are affected. To check a deployment, look up the installed QRadar EDR version and see whether it falls in that range.Source: ibm.com
How do I fix CVE-2026-91869?
Upgrade to IBM Security QRadar EDR 3.12.27, which IBM says addresses this vulnerability.Source: ibm.com