Skip to main content
VulnerabilityPublished

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

Affects IBM watsonx.dataSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavencom.ibm/watsonx.datapkg:maven/com.ibm/watsonx.dataOther threatsAffected
  • =2.2
Fixed in–

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

AI-suggested

Organizations should immediately audit their IBM watsonx.data deployments to identify affected versions (2.2 through 2.2.1) and restrict access to ingestion pods to trusted, authenticated users only. Implement strict resource quotas and limits at the container orchestration level (e.g., Kubernetes resource limits) to prevent any single ingestion pod from consuming excessive CPU or memory resources. Monitor ingestion pod resource usage continuously with alerting for abnormal spikes that could indicate exploitation attempts. Employ network segmentation and access controls to limit exposure of ingestion services. Until IBM releases official patches, consider deploying temporary throttling mechanisms or rate limiting on ingestion requests. Review and enforce strong authentication and credential management policies to reduce the risk of credential compromise. Stay informed on IBM advisories for patch releases and apply updates promptly once available. Conduct regular penetration testing and vulnerability assessments focused on resource exhaustion scenarios.

Description

IBM watsonx.data 2.2 through 2.2.1 could allow an authenticated user to cause a denial of service through ingestion pods due to improper allocation of resources without limits.

References

Community reviews

Loading reviews…