{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7589 exists.","fix":"No fix has been published for CVE-2026-7589 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7589 is a medium-severity path traversal vulnerability in ghantakiran splunk-mcp-integration, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7589 and fix it if it is affected.\n\nWhat it is: CVE-2026-7589 is a medium-severity path traversal vulnerability in ghantakiran splunk-mcp-integration, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7589 exists.\n\nAffected product: ghantakiran splunk-mcp-integration. 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-2026-7589/ (Markdown: https://insights.sbomify.com/CVE-2026-7589/index.md)","id":"CVE-2026-7589","markdown":"https://insights.sbomify.com/CVE-2026-7589/index.md","name":"CVE-2026-7589","record":{"aliases":["GHSA-cr5w-67cm-wr78"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk MCP integration","requires_auth":"none","summary":"Remote attackers can exploit a path traversal vulnerability in the CSV export function to read or modify arbitrary files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A vulnerability was determined in ghantakiran splunk-mcp-integration up to 0b86b09d5e5adf0433acd43c975951224613a1a6. Impacted is the function create_csv_export of the file services/csv-export-service/app/api/v1/endpoints/csv_export.py of the component CSV Export. This manipulation of the argument job_name causes path traversal. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"ghantakiran splunk-mcp-integration CSV Export csv_export.py create_csv_export path traversal","id":"CVE-2026-7589","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"eyal-gor p_69_branch_monkey_mcp Preview Endpoint advanced.py os command injection","id":"CVE-2026-7590"},"packages":[],"prev":{"headline":"ggerve coding-standards-mcp server.py get_best_practices path traversal","id":"CVE-2026-7588"},"products":["splunk-mcp-integration"],"published":"2026-05-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-04","vendors":["ghantakiran"]},"summary":"Remote attackers can exploit a path traversal vulnerability in the CSV export function to read or modify arbitrary files.","url":"https://insights.sbomify.com/CVE-2026-7589/"}