Description

A vulnerability was found in PV-Bhat gemsuite-mcp 1.0.0. Affected by this issue is some unknown functionality of the file src/handlers/unified-gemini.ts of the component gemini_search/gemini_reason/gemini_process/gemini_analyze. The manipulation of the argument file_path/file_paths results in path traversal. The attack must be initiated from a local position. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "3.3",
  "pubDate": "2026-08-09T21:16:59.193Z",
  "pubdate": "2026-08-09T21:16:59.193Z",
  "executiveSummary": "A path traversal vulnerability has been identified in PV-Bhat gemsuite-mcp version 1.0.0, specifically within components gemini_search, gemini_reason, gemini_process, and gemini_analyze. The flaw arises from the improper sanitization of the file_path and file_paths arguments processed by the application.\nSuccessful exploitation of this vulnerability allows local attackers to traverse the directory structure and access arbitrary files outside the intended operational scope on the underlying filesystem.\nThe risk implication is rated as significant, as unauthorized file read operations could expose sensitive system data, configuration files, or source code depending on the execution privileges of the process.\nThe attack vector requires local positioning to initiate the exploit against the vulnerable component. The vendor was notified via an early issue report but has not yet provided an official response or patch.",
  "technicalDetails": "The vulnerability exists in the src/handlers/unified-gemini.ts file of the gemsuite-mcp component stack, specifically across functions handling gemini_search, gemini_reason, gemini_process, and gemini_analyze. The root cause stems from insufficient validation and sanitization of user-supplied input parameters, specifically file_path and file_paths.\nWhen the application handles requests containing these arguments, it fails to properly neutralize directory traversal sequences such as dot-dot-slash (../) patterns. Consequently, an attacker can manipulate these input fields to traverse the hierarchical directory tree and reference files residing outside the application's designated root directory.\nThe attack flow proceeds as follows: First, the local attacker constructs a malicious payload containing relative path traversal sequences targeting a sensitive file on the host system. Second, the attacker invokes one of the vulnerable handlers (gemini_search, gemini_reason, gemini_process, or gemini_analyze) passing the crafted payload through the file_path or file_paths argument. Third, the src/handlers/unified-gemini.ts script processes the parameter without adequate bounds checking or path normalization.\nFinally, the underlying file system operations access and potentially return the contents of the targeted file back through the application interface, leading to unauthorized information disclosure.\nThe affected version is strictly 1.0.0. Exploitation requires local access to the system executing the software, and authentication requirements depend on the surrounding environment implementation. Network exposure is localized unless the vulnerable component is exposed via an insecure local service interface. Post-exploitation impact is characterized by the compromise of confidentiality regarding accessible local files."
}