CVE-2026-84034

IBM Guardium Data Protection is affected by multiple vulnerabilities.

Published Sep 18, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
IBM Guardium Data Protection 12.2 is vulnerable to a hardcoded credentials vulnerability in the hardware_assess/obstore binaries. A low-privileged authenticated user can recover hardcoded product master secrets, potentially resulting in unauthorized access to the internal database and compromise of sensitive system information.

Analysis

AI-generated

Technical impact

IBM Guardium Data Protection 12.2 contains a hardcoded credentials flaw in the hardware_assess/obstore binaries. A low‑privileged authenticated user can extract the product master secrets, enabling an attacker to authenticate to the internal database as a privileged entity and compromise sensitive system data. The vulnerability is a classic insecure credential issue (CWE-798).

Affected Systems

IBM Guardium Data Protection 12.2 running on Linux is affected. The fix is available through IBM Fix Central and is linked in the advisory. No other versions or platforms are listed as impacted in the current data.

Risk and Exploitability

The CVSS score of 8.8 classifies the issue as high severity. The EPSS score of <1% indicates a very low but nonzero probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that the likely attack vector is local and authenticated; an attacker with low‑privileged credentials must execute the hardware_assess/obstore binaries to recover the hardcoded master secrets and then use those secrets to gain elevated access to the internal database. This local, authenticated path and the requirement for session‑level access make widespread automation unlikely, but the high severity and possible data compromise remain significant risks.

Remediation

Vendor Solution

IBM encourages customers to update their systems promptly.  ProductVersions FixIBM Guardium Data Protection12.2 https://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Information+Management/InfoSphere+Guardium&release=12.2&platform=Linux&function=fixId&fixids=SqlGuard_12.0p233_FixPack&includeSupersedes=0&source=fc


OpenCVE Recommended Actions

  • Apply the IBM guardium_data_protection 12.2 fix from the Fix Central link that removes the hardcoded credentials from the hardware_assess/obstore binaries.
  • Replace or patch the vulnerable binaries on all affected systems to eliminate hardcoded secrets and ensure the binaries are signed and verifiable.
  • Restrict file permissions and execution rights for the hardware_assess/obstore binaries to the minimal set of privileged users and enable auditing of any accesses to these files.

Generated by OpenCVE AI on September 19, 2026 at 15:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description IBM Guardium Data Protection 12.2 is vulnerable to a hardcoded credentials vulnerability in the hardware_assess/obstore binaries. A low-privileged authenticated user can recover hardcoded product master secrets, potentially resulting in unauthorized access to the internal database and compromise of sensitive system information.
Title IBM Guardium Data Protection is affected by multiple vulnerabilities.
First Time appeared Ibm
Ibm guardium Data Protection
Weaknesses CWE-798
CPEs cpe:2.3:a:ibm:guardium_data_protection:12.2.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:guardium_data_protection:12.2:*:*:*:*:*:*:*
Vendors & Products Ibm
Ibm guardium Data Protection
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
ibm
Published
Updated
Sep 23, 2026, 3:55 AM
Reserved
Sep 1, 2026, 2:06 AM
Status
Analyzed
Published
Sep 18, 2026, 8:17 PM
Modified
Oct 6, 2026, 4:24 PM