IBM
Security QRadar EDR
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2024-45636 | 11 Jun 2026 | Security QRadar EDR: 3.12.0 ≤ 3.12.24 | IBM encourages customers to update their systems promptly.; ProductFix versionIBM Security QRadar EDR3.12.25; The IBM Security QRadar EDR operator can be upgraded automatically when new compatible versions are available. However, you can control whether an operator is upgraded automatically by setting an approval strategy.; Two approval strategies are available:; * Automatic (default) - New operator versions are installed automatically when they are available on the subscription channel.; * Manual - When a new operator version is available on the subscription channel, the subscription indicates that an update is available, but you must approve the update manually.; For more information about the manual installation process, view Installing QRadar EDR https://www.ibm.com/docs/en/security-qradar-edr/3.12 | Update reference ↗ |
| CVE-2025-36376 | 17 Feb 2026 | 3.12 ≤ 3.12.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36377 | 17 Feb 2026 | 3.12 ≤ 3.12.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36379 | 17 Feb 2026 | 3.12 ≤ 3.12.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-45100 | 7 Jan 2025 | 3.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-45640 | 7 Jan 2025 | 3.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-33860 | 10 Jul 2024 | 3.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-33859 | 10 Jul 2024 | 3.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-35006 | 10 Jul 2024 | 3.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
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.