{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-36319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-36319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-36319 is a medium-severity denial of service vulnerability in IBM watsonx.data intelligence, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-36319 and fix it if it is affected.\n\nWhat it is: CVE-2025-36319 is a medium-severity denial of service vulnerability in IBM watsonx.data intelligence, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-36319 in the wild and no public exploit code.\n\nAffected product: IBM watsonx.data intelligence. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-36319/ (Markdown: https://insights.sbomify.com/CVE-2025-36319/index.md)","id":"CVE-2025-36319","markdown":"https://insights.sbomify.com/CVE-2025-36319/index.md","name":"CVE-2025-36319","record":{"aliases":["GHSA-8g9m-mqc8-rhxx"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM watsonx.data intelligence","requires_auth":"low_privilege","summary":"An authenticated user can cause a temporary denial of service in IBM watsonx.data intelligence via a specially crafted HTTP request due to improper resource throttling.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"watsonx.data_intelligence","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Vulnerabilities found in Watson Data Intelligence","id":"CVE-2025-36319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Vulnerabilities found in Watson Data Intelligence","id":"CVE-2025-36320"},"packages":[],"prev":{"headline":"IBM Planning Analytics Information Disclosure","id":"CVE-2025-36299"},"products":["watsonx.data intelligence"],"published":"2026-06-30","related":[{"cvss_score":6.5,"headline":"Vulnerabilities found in Watson Data Intelligence","id":"CVE-2025-36327","kev_date_added":null,"published":"2026-06-30"},{"cvss_score":6.4,"headline":"Vulnerabilities found in Watson Data Intelligence","id":"CVE-2025-36320","kev_date_added":null,"published":"2026-06-30"},{"cvss_score":5.9,"headline":"Vulnerabilities found in Watson Data Intelligence","id":"CVE-2025-12530","kev_date_added":null,"published":"2026-06-30"},{"cvss_score":5.9,"headline":"Cleartext Transmission of Sensitive Information in Watson Data Intelligence","id":"CVE-2025-36336","kev_date_added":null,"published":"2026-06-30"},{"cvss_score":5.7,"headline":"Vulnerabilities found in Watson Data Intelligence","id":"CVE-2025-36321","kev_date_added":null,"published":"2026-06-30"},{"cvss_score":5.4,"headline":"Vulnerabilities found in Watson Data Intelligence","id":"CVE-2025-36323","kev_date_added":null,"published":"2026-06-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-01","vendors":["IBM"]},"summary":"An authenticated user can cause a temporary denial of service in IBM watsonx.data intelligence via a specially crafted HTTP request due to improper resource throttling.","url":"https://insights.sbomify.com/CVE-2025-36319/"}