Skip to main content
VulnerabilityPublished

CVE-2025-36319: IBM watsonx.data intelligence · Unthrottled Resource Allocation

Affects IBM watsonx.data intelligenceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
IBMwatsonx.data intelligenceAffected
  • =5.2.0, 5.2.1, 5.2.2, 5.3.0
Fixed in–
Mavencom.ibm/watsonx.data-intelligencepkg:maven/com.ibm/watsonx.data-intelligenceOther threatsAffected
  • >=5.2.0 <=5.2.2
  • =5.3.0
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:ibm:watsonxdata_intelligence:5.2.0:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, monitor for unusual resource consumption from authenticated users and consider implementing external rate limiting or access controls to mitigate potential abuse.

Description

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.

References

Community reviews

Loading reviews…