dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2025-25022

HIGH · 8.8 CVSS v3.1 Published 2025-06-03
Fix available
A fix is available. Upgrade to after 1.11.2.0 or later.
See remediation →
93/100
Remediation priority · Urgent
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 QRadar Suite Software 1.10.12.0 through 1.11.2.0 and IBM Cloud Pak for Security 1.10.0.0 through 1.10.11.0 could allow an unauthenticated user in the environment to obtain highly sensitive information in configuration files.

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 QRadar Suite Software versions 1.10.12.0 through 1.11.2.0 and IBM Cloud Pak for Security versions 1.10.0.0 through 1.10.11.0 contain a vulnerability allowing unauthenticated users within the environment boundary to obtain highly sensitive information from configuration files, likely through improper access controls on sensitive config data.

MitigationApply the vendor-supplied security patch for the specific version in use. If patching is immediately infeasible, restrict network access to the affected systems and audit configurations for exposed sensitive data.

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
Cloud Pak For SecurityApplication
Affected:>= 1.10.0.0, <= 1.10.11.0
Qradar SuiteApplication
Affected:>= 1.10.12.0, <= 1.11.2.0

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the installed IBM product
    Locate the installed IBM QRadar Suite or IBM Cloud Pak for Security installation and confirm the product name. This may be found via system inventory, installed packages, or the product's web interface.
    Affected if The system runs IBM QRadar Suite or IBM Cloud Pak for Security
  2. Check the installed version
    Retrieve the installed version number of IBM QRadar Suite or IBM Cloud Pak for Security. This is typically available in the product's web interface under About or System Settings, or via command-line tools provided by the product.
    Affected if The version falls within 1.10.12.0 to 1.11.2.0 for QRadar Suite, or 1.10.0.0 to 1.10.11.0 for Cloud Pak for Security
  3. Locate configuration files containing sensitive data
    Identify configuration files used by the IBM product that may contain sensitive information such as credentials, API keys, or security settings. Common locations include the product's config directory, data directory, or deployment configurations.
    Affected if Configuration files with sensitive data exist on the system
  4. Verify access controls on sensitive configuration files
    Test or inspect file permissions on identified configuration files to determine if unauthenticated or unauthorized users can read them. On Linux systems, use 'ls -la' to check permissions. On Windows, check ACLs or use icacls.
    Affected if Configuration files with sensitive data are readable by unauthenticated users or users without proper authorization

You are affected if the installed version falls within the affected ranges AND sensitive configuration files are accessible without authentication due to improper access controls.

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 a release after 1.11.2.0
Interim mitigation

Apply the vendor-supplied security patch for the specific version in use. If patching is immediately infeasible, restrict network access to the affected systems and audit configurations for exposed sensitive data.

Recommended fix Moderate confidence

Cloud Pak for Security: 1.10.12.0 or later; QRadar Suite: 1.11.3.0 or later

  1. 1. Back up all current configuration files and data stores for the QRadar Suite or Cloud Pak for Security installation
  2. 2. Review IBM's official security bulletin for this CVE for any specific interim fix instructions
  3. 3. Schedule a maintenance window as upgrades may require downtime
  4. 4. For Cloud Pak for Security: Upgrade from 1.10.x.x to version 1.10.12.0 or later
  5. 5. For QRadar Suite: Upgrade from 1.10.12.0-1.11.2.0 to version 1.11.3.0 or later
  6. 6. After upgrade, verify that configuration files no longer contain plaintext sensitive information
  7. 7. Rotate any credentials that may have been exposed before the vulnerability was known
  8. 8. Test all integrations and authentication flows to ensure proper operation
Caveat Upgrade may require downtime and could include changes to configuration formats or dependencies; review IBM's upgrade documentation for migration requirements

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

Fix this in Cloud Pak For Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25022 — 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-25022 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