CVE-2026-87980
CVE-2026-87980 is a low-severity vulnerability in Ibm Guardium Data Protection with a CVSS 3.x base score of 3.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.
Key facts
- Severity: Low (CVSS 3.x base score 3.1)
- EPSS exploit prediction: 0% (5th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-532
- Affected product: Ibm Guardium Data Protection
- Published:
- Last modified:
Description
IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a local attacker to obtain sensitive information due to cleartext storage of sensitive information in logs.
Frequently asked questions
- What is CVE-2026-87980?
- IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a local attacker to obtain sensitive information due to cleartext storage of sensitive information in logs.
- How severe is CVE-2026-87980?
- CVE-2026-87980 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
- Is CVE-2026-87980 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-87980?
- CVE-2026-87980 affects Ibm Guardium Data Protection. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-87980?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2026-87980 published?
- CVE-2026-87980 was published on 2026-10-08 and last updated on 2026-10-15.
References
Affected products (1)
- cpe:2.3:a:ibm:guardium_data_protection:*:*:*:*:*:*:*:*
More vulnerabilities in Ibm Guardium Data Protection
- CVE-2026-84078 — Critical (CVSS 9.9): IBM Guardium Data Protection 12.2 is vulnerable to a missing authentication vulnerability in the LoadBalancerServlet.…
- CVE-2026-84075 — Critical (CVSS 9.9): IBM Guardium Data Protection 12.2 could allow a remote attacker to bypass security restrictions due to missing…
- CVE-2026-84064 — Critical (CVSS 9.9): IBM Guardium Data Protection 12.2 could allow a remote authenticated attacker to execute arbitrary SQL commands due to…
- CVE-2026-80442 — Critical (CVSS 9.9): IBM Guardium Data Protection 12.2 is vulnerable to an authenticated OS command injection vulnerability in the…
- CVE-2026-84249 — Critical (CVSS 9.8): IBM Guardium Data Protection 12.2, and 12.2.2 could allow a remote attacker to execute arbitrary management operations…
- CVE-2026-80381 — Critical (CVSS 9.8): IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to execute unauthorized SQL statements…
All CVEs affecting Ibm Guardium Data Protection →
Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities
- CVE-2026-73100 — Critical (CVSS 10.0): Insertion of Sensitive Information into Log File vulnerability in Apache Juneau. The default REST server call logger…
- CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
- CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
- CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
- CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
- CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →