CVE-2025-36143
CVE-2025-36143 is a medium-severity vulnerability in Ibm Watsonx.data with a CVSS 3.x base score of 4.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-78.
Key facts
- Severity: Medium (CVSS 3.x base score 4.7)
- EPSS exploit prediction: 0% (27th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-29862
- Weakness: CWE-78
- Affected product: Ibm Watsonx.data
- Published:
- Last modified:
Description
IBM Lakehouse (watsonx.data 2.2) could allow an authenticated privileged user to execute arbitrary commands on the system due to improper validation of user supplied input.
Frequently asked questions
- What is CVE-2025-36143?
- IBM Lakehouse (watsonx.data 2.2) could allow an authenticated privileged user to execute arbitrary commands on the system due to improper validation of user supplied input.
- How severe is CVE-2025-36143?
- CVE-2025-36143 has a CVSS 3.x base score of 4.7, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
- Is CVE-2025-36143 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-36143?
- CVE-2025-36143 affects Ibm Watsonx.data. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2025-36143?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2025-36143 have an EU (EUVD) identifier?
- Yes. CVE-2025-36143 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-29862.
- When was CVE-2025-36143 published?
- CVE-2025-36143 was published on 2025-09-18 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:ibm:watsonx.data:2.2:*:*:*:*:*:*:*
More vulnerabilities in Ibm Watsonx.data
- CVE-2025-36140 — Medium (CVSS 6.5): IBM watsonx.data 2.2 through 2.2.1 could allow an authenticated user to cause a denial of service through ingestion…
- CVE-2025-36335 — Medium (CVSS 6.2): IBM watsonx.data intelligence 5.2.0, 5.2.1, 5.3.0, 5.3.1 stores user credentials in plain text which can be read by a…
- CVE-2025-36139 — Medium (CVSS 5.5): IBM Lakehouse (watsonx.data 2.2) is vulnerable to stored cross-site scripting. This vulnerability allows a privileged…
- CVE-2025-36145 — Medium (CVSS 5.4): IBM watsonx.data 2.2 through 2.3.1 IBM Lakehouse does not properly restrict inbound and outbound connections which…
- CVE-2025-36180 — Medium (CVSS 5.3): IBM watsonx.data 2.2 through 2.3 IBM Lakehouse does not properly restrict communication between pods which could allow…
- CVE-2025-36146 — Medium (CVSS 4.3): IBM Lakehouse (watsonx.data 2.2) could allow an authenticated user to obtain sensitive server component version…
All CVEs affecting Ibm Watsonx.data →
Other CWE-78 (OS Command Injection) vulnerabilities
- CVE-2026-19188 — Critical (CVSS 10.0): A critical OS command injection vulnerability has been identified in the Haiwell IoT Cloud HMI Gateway product. The…
- CVE-2026-48362 — Critical (CVSS 10.0): ColdFusion is affected by an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')…
- CVE-2026-16812 — Critical (CVSS 10.0): VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue may allow a remote attacker to access…
- CVE-2026-6516 — Critical (CVSS 10.0): Zohocorp ManageEngine ADAudit Plus versions before 8606 are affected by Unauthenticated Remote code execution due to…
- CVE-2026-46339 — Critical (CVSS 10.0): 9Router is an AI router & token saver. From 0.4.30 until 0.4.37, 9Router's src/proxy.js middleware did not protect…
- CVE-2026-59726 — Critical (CVSS 10.0): Ruflo is an agent meta-harness for Claude Code and Codex. Prior to 3.16.3, ruflo's default docker-compose deployment…