CVE-2025-36324 Overview
CVE-2025-36324 is a Server-Side Request Forgery (SSRF) vulnerability affecting IBM watsonx.data intelligence versions 5.2.0, 5.2.1, 5.2.2, and 5.3.0. The flaw allows an authenticated attacker to coerce the application into sending unauthorized HTTP requests from the server. This capability enables internal network enumeration and can facilitate follow-on attacks against services reachable from the watsonx.data intelligence host. The weakness is tracked under CWE-918.
Critical Impact
An authenticated attacker can pivot through the watsonx.data intelligence server to reach internal services, enumerate the network, and stage additional attacks against otherwise unreachable systems.
Affected Products
- IBM watsonx.data intelligence 5.2.0
- IBM watsonx.data intelligence 5.2.1, 5.2.2
- IBM watsonx.data intelligence 5.3.0
Discovery Timeline
- 2026-06-30 - CVE-2025-36324 published to NVD
- 2026-07-01 - Last updated in NVD database
Technical Details for CVE-2025-36324
Vulnerability Analysis
CVE-2025-36324 is a Server-Side Request Forgery flaw in IBM watsonx.data intelligence. The application accepts user-controlled input that is later used to construct outbound HTTP requests without sufficient validation of the destination. An authenticated attacker can supply crafted URLs that the server dereferences on the attacker's behalf.
Because the request originates from the watsonx.data intelligence host, it inherits the trust relationships of that server. This means an attacker can probe internal-only endpoints, cloud metadata services, and administrative interfaces that are not exposed externally. The EPSS score is 0.27%, and no public exploit is currently available.
Root Cause
The root cause is missing or insufficient validation of URLs and hostnames supplied to functionality that performs outbound requests. The application does not enforce an allowlist of permitted destinations and does not restrict access to internal address ranges. As a result, user-supplied targets are treated as trusted destinations, matching the pattern described in CWE-918: Server-Side Request Forgery.
Attack Vector
Exploitation requires network access to the watsonx.data intelligence interface and valid authenticated credentials with low privileges. The attacker submits a request containing a URL that points to an internal resource such as an internal API, a database management interface, or a cloud metadata endpoint. The server issues the request and, depending on the feature invoked, may return response data or timing signals that reveal internal service state.
No user interaction is required beyond the attacker's own actions. See the IBM Support Page for vendor technical details.
Detection Methods for CVE-2025-36324
Indicators of Compromise
- Outbound HTTP requests from the watsonx.data intelligence server to internal IP ranges such as 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 that do not match documented integration destinations.
- Requests from the application host to cloud metadata endpoints such as 169.254.169.254.
- Repeated outbound connection attempts to sequential internal addresses or ports indicative of network enumeration.
Detection Strategies
- Review watsonx.data intelligence application logs for user-supplied URL parameters targeting loopback, link-local, or private address space.
- Correlate authenticated session identifiers with outbound request destinations to identify users triggering anomalous server-side requests.
- Compare current outbound traffic patterns from the application host against a baseline of expected integration endpoints.
Monitoring Recommendations
- Forward web server, proxy, and firewall logs from the watsonx.data intelligence host to a centralized analytics platform for outbound request review.
- Alert on any request from the application server to cloud instance metadata services or unexpected internal management ports.
- Track authenticated API calls that accept URL or hostname parameters and flag deviations from typical usage.
How to Mitigate CVE-2025-36324
Immediate Actions Required
- Apply the fixes referenced on the IBM Support Page for affected watsonx.data intelligence versions.
- Review authentication and role assignments to ensure only required users retain access to features that perform outbound requests.
- Audit recent outbound traffic from the watsonx.data intelligence host for evidence of internal reconnaissance.
Patch Information
IBM has published remediation guidance for CVE-2025-36324 on the IBM Support Page. Administrators running watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, or 5.3.0 should follow the vendor's upgrade instructions and validate the version after deployment.
Workarounds
- Place the watsonx.data intelligence host behind an egress proxy that enforces an allowlist of permitted destinations.
- Block the application host from reaching internal management networks and cloud metadata services at the network layer.
- Restrict access to features that accept user-supplied URLs to a minimal set of trusted administrators until patches are applied.
# Example egress restriction using iptables to block metadata service access
iptables -A OUTPUT -d 169.254.169.254 -j DROP
iptables -A OUTPUT -d 10.0.0.0/8 -p tcp --dport 22 -j DROP
iptables -A OUTPUT -d 172.16.0.0/12 -p tcp --dport 3306 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

