Skip to main content
VulnerabilityPublished Updated

CVE-2025-25020: IBM QRadar Suite Software · Improper Validation of Specified Type of Input

Affects IBM QRadar Suite SoftwareSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBM QRadar Suite SoftwareAffected
  • =1.10.12.0
  • <=1.11.2.0
Fixed in–

AI-suggested

Organizations should prioritize the following mitigation steps: 1) Monitor IBM’s official security advisories closely for patches or updates addressing CVE-2025-25020 and apply them promptly once available. 2) Restrict access to the QRadar and Cloud Pak for Security APIs to only trusted and necessary users and systems, employing network segmentation and firewall rules to limit exposure. 3) Enforce strict authentication and authorization policies, including multi-factor authentication (MFA) for all users with access to the affected systems. 4) Implement robust logging and monitoring of API usage to detect anomalous or suspicious activity that could indicate exploitation attempts. 5) Conduct regular security audits and penetration testing focused on API endpoints to identify and remediate input validation weaknesses proactively. 6) Prepare incident response plans that include procedures for handling potential DoS conditions affecting security infrastructure. These measures go beyond generic advice by focusing on access control, monitoring, and readiness specific to the nature of this vulnerability.

Description

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 authenticated user to cause a denial of service due to improperly validating API data input.

References

Community reviews

Loading reviews…