dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7589

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Path traversal vulnerability in the create_csv_export function of the Splunk MCP integration's CSV export service. The job_name parameter is not properly sanitized, allowing attackers to use directory traversal sequences (e.g., ../../../) to access files outside the intended export directory.

MitigationImplement strict input validation on the job_name parameter using basename() to strip directory components and validate the final path is within the intended directory. Alternatively, implement allowlisting of permitted job names.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Splunk MCP integration is installed
    Search for MCP-related configurations in Splunk app directories or check for 'mcp' in splunkd logs, configuration files, or installed apps. Look for files named 'mcp.conf' or directories containing 'mcp' in the Splunk installation path.
    Affected if The Splunk MCP integration package or app is present in the environment
  2. Locate the CSV export service module
    Search for Python files containing 'create_csv_export' or 'csv_export' within the MCP integration directory structure. Common paths include $SPLUNK_HOME/etc/apps/<mcp_app>/bin/ or similar.
    Affected if The create_csv_export function exists in the installed MCP integration
  3. Verify job_name parameter handling
    Inspect the create_csv_export function source code. Search for the job_name parameter usage. Check if path sanitization functions like os.path.basename() are applied before using the parameter in file operations.
    Affected if The job_name parameter is used directly in file path operations without sanitization using basename() or path validation
  4. Test for path traversal vulnerability
    If the function is accessible via API or CLI, attempt a controlled test with a job_name containing '../../' sequences to observe if file access occurs outside the intended directory. Alternatively, review access logs for unusual path patterns.
    Affected if The function allows directory traversal sequences in job_name and accesses paths outside the designated export directory
  5. Check Splunk version and MCP integration version
    Run 'splunk version' to obtain the Splunk platform version. Check the MCP integration app version in $SPLUNK_HOME/etc/apps/<mcp_app>/default/app.conf or via Splunk Web management interface.
    Affected if The Splunk platform or MCP integration version is within an affected range and vulnerable code is present

The environment is affected if the Splunk MCP integration is installed with the vulnerable create_csv_export function that does not sanitize the job_name parameter before using it in file path operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the job_name parameter using basename() to strip directory components and validate the final path is within the intended directory. Alternatively, implement allowlisting of permitted job names.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7589 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data