{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-36180 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-36180 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-36180 is a medium-severity missing authorization vulnerability in IBM watsonx.data, published on 30 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-36180 and fix it if it is affected.\n\nWhat it is: CVE-2025-36180 is a medium-severity missing authorization vulnerability in IBM watsonx.data, published on 30 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-36180 in the wild and no public exploit code.\n\nAffected product: IBM watsonx.data. 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-36180/ (Markdown: https://insights.sbomify.com/CVE-2025-36180/index.md)","id":"CVE-2025-36180","markdown":"https://insights.sbomify.com/CVE-2025-36180/index.md","name":"CVE-2025-36180","record":{"aliases":["GHSA-842g-rrpf-rmq9"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM watsonx.data","requires_auth":"none","summary":"Attackers can transfer data between pods without restrictions due to inadequate communication controls in IBM watsonx.data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"watsonx.data","vendor":"ibm"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"}],"description":"IBM watsonx.data 2.2 through 2.3 IBM Lakehouse does not properly restrict communication between pods which could allow an attacker to transfer data between pods without restrictions.","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":"Inadequate Pod Communication Restrictions, affects watsonx.data","id":"CVE-2025-36180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Privileged User File Upload Vulnerability Leading to Limited Server-Side Execution affects watsonx.data","id":"CVE-2025-36183"},"packages":[],"prev":{"headline":"Multiple vulnerabilities in IBM Controller","id":"CVE-2025-36178"},"products":["watsonx.data"],"published":"2026-04-30","related":[{"cvss_score":6.5,"headline":"IBM watsonx.data Denial of Service","id":"CVE-2025-36140","kev_date_added":null,"published":"2025-12-08"},{"cvss_score":6.2,"headline":"Vulnerabilities found","id":"CVE-2025-36335","kev_date_added":null,"published":"2026-04-30"},{"cvss_score":5.5,"headline":"IBM watsonx.data cross-site scripting","id":"CVE-2025-36139","kev_date_added":null,"published":"2025-09-18"},{"cvss_score":5.4,"headline":"Multiple Vulnerabilities in watsonx.data","id":"CVE-2025-36145","kev_date_added":null,"published":"2026-05-26"},{"cvss_score":4.7,"headline":"IBM watsonx.data command execution","id":"CVE-2025-36143","kev_date_added":null,"published":"2025-09-18"},{"cvss_score":4.3,"headline":"IBM watsonx.data information disclosure","id":"CVE-2025-36146","kev_date_added":null,"published":"2025-09-18"}],"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-05-01","vendors":["IBM"]},"summary":"Attackers can transfer data between pods without restrictions due to inadequate communication controls in IBM watsonx.data.","url":"https://insights.sbomify.com/CVE-2025-36180/"}