CVE-2025-14753
CVE-2025-14753 is a high-severity vulnerability in Ibm Cloud Pak For Data with a CVSS 3.x base score of 7.5. 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-22.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- EPSS exploit prediction: 1% (51st percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-22
- Affected product: Ibm Cloud Pak For Data
- Published:
- Last modified:
Description
IBM Cloud Pak for Data 5.1.2 could allow a remote attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system.
Frequently asked questions
- What is CVE-2025-14753?
- IBM Cloud Pak for Data 5.1.2 could allow a remote attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system.
- How severe is CVE-2025-14753?
- CVE-2025-14753 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
- Is CVE-2025-14753 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-14753?
- CVE-2025-14753 affects Ibm Cloud Pak For Data. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2025-14753?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2025-14753 published?
- CVE-2025-14753 was published on 2026-09-18 and last updated on 2026-10-14.
References
Affected products (1)
- cpe:2.3:a:ibm:cloud_pak_for_data:5.1.2:*:*:*:*:*:*:*
More vulnerabilities in Ibm Cloud Pak For Data
- CVE-2025-14754 — High (CVSS 8.8): IBM Cloud Pak for Data 5.1.2 could allow an authenticated user to execute arbitrary commands with elevated privileges…
- CVE-2022-36769 — High (CVSS 7.2): IBM Cloud Pak for Data 4.5 and 4.6 could allow a privileged user to upload malicious files of dangerous types that can…
- CVE-2023-26023 — Medium (CVSS 6.5): Planning Analytics Cartridge for Cloud Pak for Data 4.0 exposes sensitive information in logs which could lead an…
- CVE-2021-20486 — Medium (CVSS 6.5): IBM Cloud Pak for Data 3.0 could allow an authenticated user to obtain sensitive information when installed with…
- CVE-2025-0719 — Medium (CVSS 6.1): IBM Cloud Pak for Data 4.0.0 through 4.8.5 and 5.0.0 is vulnerable to cross-site scripting. This vulnerability allows…
- CVE-2023-27540 — Medium (CVSS 5.9): IBM Watson CP4D Data Stores 4.6.0 does not properly allocate resources without limits or throttling which could allow a…
All CVEs affecting Ibm Cloud Pak For Data →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-77312 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429…
- CVE-2026-121351 — Critical (CVSS 10.0): Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')…
- CVE-2026-121489 — Critical (CVSS 10.0): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau. The…
- CVE-2026-122013 — Critical (CVSS 10.0): A vulnerability was detected in Comfast CF-WR632AX 2.6.0.1. Affected by this vulnerability is an unknown functionality…
- CVE-2026-61738 — Critical (CVSS 10.0): SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to…
- CVE-2026-112690 — Critical (CVSS 10.0): This issue was addressed with improved input validation. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2…