CVE-2025-25026: IBM Security Guardium information disclosure

Published May 27, 2025
·
Updated

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

Other sources

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

IBM

Affected Software

4 affected components
IBM Security Guardium
IBM Security Guardium=12.0
IBM Guardium Data Protection<=12.0
IBM Guardium Data Protection<=12.1

Remediation

Information

IBM encourages customers to update their systems promptly. IBM Guardium Data Protection 12.0 https://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Informat... https://www.ibm.com/support/fixcentral/swg/quickorder

Event History

May 27, 2025
CVE Published
via IBM·12:00 AM
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
May 28, 2025
CVE Published
via MITRE·01:11 AM
Data Sourced
via MITRE·01:11 AM
RemedyDescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-25026?

CVE-2025-25026 is deemed to be a medium severity vulnerability as it allows authenticated users to access sensitive information.

2

How do I fix CVE-2025-25026?

To fix CVE-2025-25026, ensure that you apply the latest security patches provided by IBM for Security Guardium 12.0.

3

What are the potential impacts of CVE-2025-25026?

The potential impacts of CVE-2025-25026 include unauthorized access to sensitive information which could lead to data breaches.

4

Who is affected by CVE-2025-25026?

Organizations using IBM Security Guardium version 12.0 may be affected by CVE-2025-25026 if they have not enforced stricter authentication checks.

5

Is there a workaround for CVE-2025-25026?

While the best approach is to apply security patches, temporarily restricting user access can help mitigate risks associated with CVE-2025-25026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203