Skip to main content
CVE-2025-25026VulnerabilityPublished Updated

CVE-2025-25026: IBM Security Guardium · Incorrect Authorization

Affects IBM Security GuardiumSource CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% 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:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
IBM Security GuardiumAffected
  • =12.0
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should prioritize the following actions: 1) Monitor IBM’s official security advisories closely for the release of patches or updates addressing CVE-2025-25026 and apply them promptly. 2) Implement strict access controls and auditing on IBM Security Guardium deployments to limit the number of users with authenticated access and to detect unusual access patterns. 3) Enforce the principle of least privilege rigorously, ensuring users have only the minimum necessary permissions to perform their roles. 4) Conduct regular reviews of user roles and permissions within Guardium to identify and remediate any excessive privileges. 5) Utilize multi-factor authentication (MFA) for all users accessing Guardium to reduce the risk of compromised credentials being used to exploit this vulnerability. 6) Employ network segmentation and monitoring to restrict and observe traffic to Guardium systems, detecting potential lateral movement by attackers. 7) Prepare incident response plans that include scenarios involving insider threats or unauthorized data access to ensure rapid containment and remediation.

Description

IBM Security Guardium 12.0 could allow an authenticated user to obtain sensitive information due to an incorrect authentication check.

References

Community reviews

Loading reviews…