CVE-2026-8862
HighCVSS 7.5Summary
IBM Netezza Software 11.3.0.3 through Interim Fix 002 has hardcoded credentials in the application source code, allowing unauthorized access to the container registry. The exposed secret enables attackers to pull private container images, potentially revealing proprietary code, configuration details, and other sensitive information.
Risk Assessment
The risk to the organization includes leakage of confidential data and source code, which may lead to security breaches and loss of competitive advantage.
Recommendation
It is recommended to immediately change the hardcoded credentials, remove them from the source code, and implement secure secret management, e.g., using an external secret store.
Other vulnerabilities in IBM Netezza Software
See all- CVE-2026-9745Medium
IBM Netezza Software 11.3.0.3 through Interim Fix 002 has operations that are performed without validating bucket ownership using the ExpectedBucketOwner parameter. This omission may allow a remote attacker to exploit misconfigurations or naming collisions to redirect application requests to an unintended S3 bucket under their control.
- CVE-2026-9744Medium
IBM Netezza Software versions 11.3.0.3 through Interim Fix 002 does not validate or improperly validates TLS certificate validation, which could allow an attacker to obtain sensitive information using man in the middle techniques.
- CVE-2026-9736Medium
IBM Netezza Software versions 11.3.0.3 through Interim Fix 002 could allow an unauthorized user to inject data into log messages due to improper neutralization of special elements when written to log files.
- CVE-2026-9036Medium
IBM Netezza Software versions 11.3.0.3 through Interim Fix 002 does not validate or improperly validates TLS certificate validation, which could allow an attacker to obtain sensitive information using man in the middle techniques.
Original NVD description (English source)
IBM Netezza Software 11.3.0.3 through Interim Fix 002 has credentials that are hardcoded in the application source code, allowing unauthorized access to the container registry. The exposed secret enables attackers to pull private container images, potentially revealing proprietary code, configuration details, and other sensitive information.