dbcve.org
Qradar EdrApplication · Ibm

CVE-2025-36379

HIGH · 7.5 CVSS v3.1 Published 2026-02-17
Fix available
A fix is available. Upgrade to 3.12.24 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM Security QRadar EDR versions 3.12 through 3.12.23 and IBM Security ReaQta implement weaker than expected cryptographic algorithms, potentially allowing attackers to decrypt highly sensitive information that was protected using these weak cryptographic methods.

MitigationOrganizations should upgrade to a patched version of the software and conduct a cryptographic assessment to identify and re-encrypt any sensitive data that may have been protected with the weak algorithms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Qradar EdrApplication
Affected:>= 3.12.0, < 3.12.24

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify QRadar EDR version
    Use the product's built-in version reporting mechanism or check the installed package version (e.g., via package manager, about dialog, or version command specific to the product)
    Affected if The installed version is 3.12.0 through 3.12.23 (any version >= 3.12.0 but < 3.12.24)
  2. Confirm product is being used for data encryption
    Review whether the QRadar EDR or ReaQta installation has been configured to encrypt sensitive data using its built-in encryption capabilities
    Affected if The product is actively encrypting sensitive data with its native encryption features in the affected version range
  3. Verify weak cryptographic algorithm usage
    Examine the product configuration or cryptographic settings to determine if weak algorithms (such as MD5, SHA1, DES, or similar) are being used for data protection
    Affected if Weak or outdated cryptographic algorithms are enabled in the product configuration

You are affected if QRadar EDR version 3.12.0 through 3.12.23 is installed and the product has been used to encrypt sensitive data using its weak cryptographic implementations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.12.24 or later
Fixed in 3.12.24
Interim mitigation

Organizations should upgrade to a patched version of the software and conduct a cryptographic assessment to identify and re-encrypt any sensitive data that may have been protected with the weak algorithms.

Recommended fix High confidence

3.12.24

  1. 1. Back up the current QRadar EDR configuration and any critical data before starting the upgrade process.
  2. 2. Download IBM Security QRadar EDR version 3.12.24 or later from the official IBM Fix Central or IBM Passport Advantage.
  3. 3. Verify the integrity of the downloaded package using checksums provided by IBM.
  4. 4. Stop the QRadar EDR services according to the official IBM documentation for your deployment model.
  5. 5. Apply the upgrade following the IBM installation and upgrade guide for QRadar EDR.
  6. 6. Verify that the upgrade was successful by checking the version number in the system information.
  7. 7. Restart QRadar EDR services and confirm all components are running properly.
  8. 8. Validate that the cryptographic improvements are functioning by reviewing system logs and running any available cryptographic verification tools.
Caveat Review IBM QRadar EDR 3.12.24 release notes for any compatibility changes or known issues before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qradar Edr Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36379 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data