Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY21 SECURITY RECORDS

IBM

Qradar

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2025-33141 18 Sep 2026 QRadar: 7.5.0 ≤ 7.5.0 UP15 Interim Fix 006 ProductVersionFixIBM QRadar SIEM 7.5.0; 7.5.0 UP16 https://www.ibm.com/support/pages/node/7283630 Update reference ↗
CVE-2026-5522 4 Sep 2026 7.5.0 ≤ 7.5.0 UP15 Interim Fix 005 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-10025 5 Aug 2026 7.6.0.0 ≤ 7.6.0.1; 7.5.0 ≤ 7.5.0 UP 15 Interim Fix 005 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13477 5 Aug 2026 7.6.0.0 ≤ 7.6.0.1; 7.5.0 ≤ 7.5.0 UP 15 Interim Fix 005 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-56462 27 May 2026 7.5.0 ≤ 7.5.0 UP15 Interim Fix 002 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13995 19 Mar 2026 7.5.0 ≤ 7.5.0 Update Pack 14 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-4980 16 Jul 2021 7.3; 7.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-4294 15 Apr 2020 7.3.3.Patch2; 7.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-4274 15 Apr 2020 7.3.0; 7.3.3.Patch2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-4272 15 Apr 2020 7.3.0; 7.3.3.Patch2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-4271 15 Apr 2020 7.3.3.Patch2; 7.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-4270 15 Apr 2020 7.3.3.Patch2; 7.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-4269 15 Apr 2020 7.3.3.Patch2; 7.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-4268 15 Apr 2020 7.3.3.Patch2; 7.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-4654 15 Apr 2020 7.3.3.Patch2; 7.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-4594 15 Apr 2020 7.3.0; 7.3.3.Patch1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-4593 15 Apr 2020 7.3.3.Patch1; 7.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-4581 9 Nov 2019 7.3.0; 7.3.2Patch4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2019-4509 9 Nov 2019 7.3.0; 7.3.2Patch4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2019-4470 9 Nov 2019 7.3.0; 7.3.2Patch4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2019-4454 9 Nov 2019 7.3.0; 7.3.2Patch4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.