EUVD-2026-26706Severity by source
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
6DescriptionCVE.org
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.
AnalysisAI
Path traversal in the CSV Export endpoint of ghantakiran's splunk-mcp-integration allows remote unauthenticated attackers to access arbitrary files on the server by manipulating the job_name parameter in the create_csv_export function. The vulnerability affects all versions up to commit 0b86b09d5e5adf0433acd43c975951224613a1a6, with publicly available exploit code disclosed via GitHub issue; no vendor patch has been released despite early notification.
Technical ContextAI
The vulnerability exists in the CSV Export component (csv_export.py) where the create_csv_export function in the v1 API endpoint fails to sanitize the job_name argument before using it in file path operations. This classic CWE-22 path traversal flaw allows attackers to inject directory traversal sequences (such as ../) to navigate outside the intended directory and access sensitive files. The affected product is a Splunk integration tool written in Python using a rolling-release continuous delivery model, meaning specific version numbers are not tracked; instead, a Git commit hash (0b86b09d5e5adf0433acd43c975951224613a1a6) marks the last known vulnerable state.
RemediationAI
No vendor-released patch is currently available; the project maintainer has not responded to the early notification despite the public disclosure. Immediate mitigation requires either removing the splunk-mcp-integration tool from production use or implementing network-layer compensating controls: restrict HTTP/HTTPS access to the CSV Export endpoint (/api/v1/endpoints/csv_export) by IP whitelist, limiting access to trusted internal administrative networks only; disable the CSV Export feature entirely if not actively used by blocking requests to the /csv_export path prefix; implement rate limiting and request validation at a reverse proxy (nginx, Apache) to reject job_name parameters containing path traversal sequences (../, ..\, encoded variants); or deploy a Web Application Firewall (WAF) rule to sanitize the job_name parameter. Organizations should monitor the GitHub repository (https://github.com/ghantakiran/splunk-mcp-integration/) and VulDB advisory (https://vuldb.com/vuln/360542) for any future security updates from the maintainer. If the tool is critical to operations, consider forking the repository to apply a local patch that sanitizes the job_name parameter by removing or rejecting ../ sequences before file path construction.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or powe
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100,
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functional
When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly re
A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an atta
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today