CVE-2026-75801

watsonx.data used a fixed cryptographic key for sensitive credentials

IBM · IBM watsonx.data · Lakehouse

First documented disclosure · Review checkpoint

Summary

A local attacker could recover sensitive credentials.

Severity and exploitation evidence

Medium · 6.2/10 · CVSS 3.1. Severity source.

Exploitation not established: Reviewed public sources describe the weakness, a correction or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

A hard-coded cryptographic key protects credential data.

Conditions required

Local access; IBM’s vector requires no privileges or user interaction.

Potential impact

Credential disclosure.

Affected versions and configurations

2.4.0 through 2.4.0 patch 8.

Fix and mitigation status

2.4.0 patch 9.

Practical next steps

Apply watsonx.data 2.4.0 patch 9 or the appropriate latest supported watsonx.data / CPD 5.4 update. IBM lists no workaround.

Operating lesson

Keep authorization, network and session controls in the server-side AI data platform.

Evidence and limits

The IBM bulletin’s initial-publication history is November 19. Its summary explicitly names 2.4.0 patch 9; the broader remediation paragraph directs users to the latest available supported level. The specific prerequisites come from IBM’s own CVSS 3.1 assessment. No neighboring dependency CVE is inferred from this mapping. CNA publication is 2026-11-19; this is distinct from the earliest reviewed public source and correction dates. ibm assessments: CVSS 3.1 6.2.

Sources