IBM Enterprise Records EUVD-2026-71150

Exploitation requires local access to the system or container environment hosting IBM Enterprise Records within CP4BA - AV:L constrains this to attackers who have already obtained a foothold on the host node, a co-located pod, or access to shared persistent storage. No system privileges are required (PR:N) once local access is achieved, but initial local access itself is a prerequisite. The cryptographic weakness is within CP4BA versions up to the listed interim fix thresholds; patched interim fix levels are not affected. There is no network-remote exploitation path. No user interaction is required once local access is established.

The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) scores 6.2 (Medium), reflecting a local attack vector with no privilege requirement and high confidentiality impact. The local attack vector (AV:L) meaningfully constrains exploitability - an attacker must first obtain local access to the CP4BA host or container environment. PR:N with AV:L suggests the encrypted material may be accessible without elevated system privileges (e.g., world-readable files or shared storage). No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog, placing exploitation risk as theoretical-but-credible rather than actively targeted. The impact is purely confidentiality-based (I:N/A:N), limiting scope to data exposure rather than system compromise. In containerized OpenShift deployments, 'local access' may include any pod co-hosted on the same node, which could broaden the realistic attacker population in multi-tenant environments.

An attacker with local access to the CP4BA OpenShift node or pod - such as a compromised co-tenant container or an insider with node-level access - reads files or storage artifacts protected by the weak cryptographic algorithm used by Enterprise Records. Using widely available cryptanalysis tools targeting the weak algorithm (e.g., offline brute force or known-plaintext attacks against DES/MD5), the attacker recovers sensitive information such as credentials, business records, or configuration secrets. No public exploit code has been identified at time of analysis.