CVE-2026-14880

watsonx.data network segmentation could allow unauthorized access

IBM · IBM watsonx.data · Lakehouse

First documented disclosure · Review checkpoint

Summary

An attacker could cross an intended network boundary.

Severity and exploitation evidence

Medium · 5.3/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

Network segmentation controls are insufficient.

Conditions required

Adjacent-network access and high-complexity conditions; IBM’s vector does not require an account.

Potential impact

Unauthorized network access with integrity impact.

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 5.3.

Sources