# CVE-2026-7589: ghantakiran splunk-mcp-integration CSV Export csv_export.py create_csv_export path traversal

> Remote attackers can exploit a path traversal vulnerability in the CSV export function to read or modify arbitrary files.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-cr5w-67cm-wr78

## What is CVE-2026-7589?

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.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-7589?


## How do I fix CVE-2026-7589?

No fix has been published for CVE-2026-7589 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7589 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7589 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7589 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7589 exists.

Affected product: ghantakiran splunk-mcp-integration. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7589/ (Markdown: https://insights.sbomify.com/CVE-2026-7589/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7589
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7589
- OSV: https://osv.dev/vulnerability/CVE-2026-7589

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7589/
Summaries are generated and may contain mistakes; the official description above is the record.