CVE-2025-36379: IBM Security QRadar EDR 3.12 through 3.12.23 IBM Security ReaQta uses weaker than expected cryptographic algor
CVE-2025-36379 is a medium-severity flaw (CVSS 5.9) affecting qradar edr. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
IBM Security QRadar EDR 3.12 through 3.12.23 IBM Security ReaQta uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
Why this priority
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.9 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 94%) |
| CISA exploited list | No |
| Weakness | CWE-326 |
| Published | 2026-02-17 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-36379?
qradar edr: upgrade to 3.12.24. Exact commands for each OS are on this page.
Is CVE-2025-36379 being exploited?
CVE-2025-36379 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-36379 affect?
CVE-2025-36379 affects qradar edr. Severity is medium (CVSS 5.9). IBM Security QRadar EDR 3.12 through 3.12.23 IBM Security ReaQta uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
How urgent is CVE-2025-36379?
Priority 27/100. Remotely exploitable, no login, no user action
Related CVEs
- CVE-2025-36377 MEDIUM 6.3 UPGRADE IBM Security QRadar EDR 3.12 through 3.12.23 does not invalidate session after a session expiration which coul