What is the CVSS score of CVE-2025-36144?

CVE-2025-36144 has a CVSS 3.1 base score of 3.3 (Low). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Watsonx Data are affected by CVE-2025-36144?

CVE-2025-36144 is a low-severity vulnerability involving log exposure (CVSS 3.3). The limited severity suggests constrained impact, typically requiring specific conditions or local access for…

How to fix or mitigate CVE-2025-36144?

During next maintenance window: Apply vendor patches when convenient. Verify log exposure controls are in place.

Watsonx Data CVE-2025-36144

LOW

Insertion of Sensitive Information into Log File (CWE-532)

2025-09-27 psirt@us.ibm.com

IBM Information Disclosure Watsonx Data

3.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

3.3 LOW

AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 19:14 vuln.today

CVE Published

Sep 27, 2025 - 01:15 nvd

LOW 3.3

DescriptionCVE.org

IBM Lakehouse (watsonx.data 2.2) stores potentially sensitive information in log files that could be read by a local user.

AnalysisAI

IBM Lakehouse (watsonx.data 2.2) stores potentially sensitive information in log files that could be read by a local user. Rated low severity (CVSS 3.3), this vulnerability is low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-532. IBM Lakehouse (watsonx.data 2.2) stores potentially sensitive information in log files that could be read by a local user. Affected products include: Ibm Watsonx.Data.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.