# IBM QRadar EDR 3.12.27 fixes two flaws affecting authenticated users

Canonical: https://www.oktsec.com/radar/ibm-qradar-edr-3-12-27
Publisher: Oktsec
Language: en
Published: 2026-11-18T11:01:56Z
Updated: 2026-11-18T11:01:56Z
Record reviewed: 2026-11-18T11:01:56Z
Latest evidence check: 2026-11-18T11:01:56Z
Disclosed: 2026-11-11

IBM fixed a weakness in the checks on one-time passwords and a separate flaw that could expose sensitive information. Both require an authenticated account and affect QRadar EDR versions 3.12 through 3.12.26.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Review this week
- Rationale: Both issues require an authenticated account. IBM provides a fix and lists no workaround.
- Evidence: Attacks not established
- Verification: Vendor confirmed
- Fix status: Fix available
- Exposure requirement: Account access required
- Vendor: IBM
- Products: IBM Security QRadar EDR
- CVEs: CVE-2026-91869, CVE-2026-91868

## Technical overview

CVE-2026-91869 concerns how QRadar EDR limits attempts to verify a time-based one-time password. CVE-2026-91868 concerns access to sensitive information: the application may let an authenticated user read data beyond their permissions. IBM describes possible impact for both issues and does not report attacks in its November 11 bulletin.

An available update can still be waiting for approval. Check the operator subscription, then verify which version is actually running.

## Recommended response

Upgrade QRadar EDR to 3.12.27. Check the operator subscription and approve the update if it uses manual approval. Verify the installed version.

Relevant to: Teams operating IBM Security QRadar EDR.

## CVE attribution

- CVE-2026-91869: IBM — IBM Security QRadar EDR; CVSS 3.1: 8.1. [Source](https://www.ibm.com/support/pages/node/7296309)
- CVE-2026-91868: IBM — IBM Security QRadar EDR; CVSS 3.1: 6.5. [Source](https://www.ibm.com/support/pages/node/7296309)

## Affected systems and fixes

### IBM Security QRadar EDR

Affected: 3.12 through 3.12.26 inclusive. Both vulnerabilities affect authenticated remote users.

Fixed release / action: 3.12.27

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.18
Checked: 2026-11-18T21:06:31.057Z

No matching CVE appears in the reviewed catalog snapshot.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-19T21:12:22.272Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-91869](https://api.first.org/data/v1/epss?cve=CVE-2026-91869): 0.32% probability of observed exploitation in the next 30 days; percentile 25.56%; score date 2026-11-19.
- [CVE-2026-91868](https://api.first.org/data/v1/epss?cve=CVE-2026-91868): 0.25% probability of observed exploitation in the next 30 days; percentile 16.37%; score date 2026-11-19.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-19T21:12:22.272Z.

### Official regional advisories

- [Vulnerabilidad en productos IBM](https://www.cert.gov.py/vulnerabilidad-en-productos-ibm-7/) — CERT-PY, Paraguay; publication 2026-11-16T12:31:46.000Z; observed 2026-11-19T21:12:22.272Z; matched by exact CVE identifier.

Publisher country does not establish victim location. Original notices may repeat the same underlying advisory.

## Response checklist

1. **Check the deployed EDR version** — Compare the installed IBM Security QRadar EDR version with the affected range, 3.12 through 3.12.26.
2. **Check upgrade approval** — Use the operator subscription to install 3.12.27. With manual approval, approve the pending update. With automatic approval, check whether the compatible version has reached the subscription channel.
3. **Verify the installed fix** — Confirm that QRadar EDR reports the corrected version after the upgrade. IBM lists no workaround for installations awaiting the fix.

## Relevance to AI environments

Check the EDR deployment that monitors your workloads and confirm its installed version.

## Sources

- [QRadar EDR security bulletin and operator upgrade guidance](https://www.ibm.com/support/pages/node/7296309) — IBM; Vendor notice; checked 2026-11-18T11:01:56Z

## Editorial record

- 2026-11-18T11:01:56Z: Added the affected QRadar EDR versions, the two authenticated vulnerabilities and operator approval guidance from IBM.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/ibm-qradar-edr-3-12-27) · [Build a response plan](https://www.oktsec.com/radar/ibm-qradar-edr-3-12-27#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=ibm-qradar-edr-3-12-27&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=ibm-qradar-edr-3-12-27&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

