CVE-2025-36319: Vulnerabilities found in Watson Data Intelligence
IBM watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, 5.3.0 could allow an authenticated user to cause a temporary denial using a specially crafted HTTP request due to improper allocation of resource throttling.
Security readout for executives and security teams
Plain-English summary
CVE-2025-36319 affects IBM watsonx.data intelligence. An authenticated user could send a specially crafted HTTP request that temporarily disrupts service. The business impact is availability loss, not data theft or data modification, based on the published CVSS metrics.
Executive priority
Treat as a moderate operational risk. Prioritize remediation where service disruption would affect analytics, data operations, or shared business workflows, especially in environments with many authenticated users.
Technical view
IBM watsonx.data intelligence versions 5.2.0, 5.2.1, 5.2.2, and 5.3.0 are affected. The issue is improper allocation of resource throttling, mapped to CWE-770. CVSS 3.1 is 4.3: network exploitable, low complexity, low privileges required, no user interaction, and low availability impact.
Likely exposure
Exposure is limited to organizations running affected IBM watsonx.data intelligence versions where authenticated users can reach the application over the network.
Exploitation context
The source bundle does not indicate active exploitation, and CISA KEV status is false. Exploitation requires authentication and appears aimed at temporary denial of service rather than confidentiality or integrity compromise.
Researcher notes
Evidence supports authenticated, network-based temporary denial of service caused by resource throttling allocation weakness. No public exploitation or detailed technical trigger is provided in the supplied sources. Avoid assuming unauthenticated exposure or broader impact.
Mitigation direction
Review IBM advisory node 7277801 for the supported fix or patch path.
Prioritize updating affected watsonx.data intelligence versions in internet-accessible or shared-user environments.
Restrict application access to trusted authenticated users where feasible.
Monitor service availability and unusual authenticated request patterns until remediated.
Validation and detection
Inventory IBM watsonx.data intelligence deployments and record installed versions.
Confirm whether any deployment runs 5.2.0, 5.2.1, 5.2.2, or 5.3.0.
Check IBM advisory for fixed versions and compare against deployed builds.
Verify authentication and network exposure controls for affected instances.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.