CVE-2026-7384: mcp-bases Path Traversal Vulnerability

CVE-2026-7384 Overview

A path traversal vulnerability has been identified in ezequiroga mcp-bases, specifically within the search_papers function of the research_server.py file. The vulnerability allows attackers to manipulate the topic argument to traverse directory structures and potentially access files outside the intended directory scope. This issue is remotely exploitable, and a public exploit has been disclosed.

Critical Impact
Remote attackers can exploit the path traversal vulnerability to access sensitive files on the server by manipulating the topic parameter in the search_papers function.

Affected Products

ezequiroga mcp-bases (commit 357ca19c7a49a9b9cb2ef639b366f03aba8bea39)
ezequiroga mcp-bases (commit c630b8ab0f970614d42da8e566e9c0d15a16414c)
Note: This product uses a rolling release model without version numbers

Discovery Timeline

2026-04-29 - CVE-2026-7384 published to NVD
2026-04-29 - Last updated in NVD database

Technical Details for CVE-2026-7384

Vulnerability Analysis

This vulnerability is classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), commonly known as Path Traversal or Directory Traversal. The flaw exists in the search_papers function within research_server.py, where user-controlled input passed through the topic argument is not properly sanitized before being used in file system operations.

When a user supplies a malicious topic value containing path traversal sequences such as ../, the application fails to validate or sanitize this input, allowing the attacker to navigate outside the intended directory structure. This can lead to unauthorized access to sensitive configuration files, application source code, or other system files accessible to the application's user context.

The network-accessible nature of this vulnerability means that remote attackers can exploit it without requiring authentication or local access to the target system, increasing the potential attack surface significantly.

Root Cause

The root cause of this vulnerability lies in the absence of proper input validation and sanitization within the search_papers function. The topic parameter is directly used in file path operations without filtering out dangerous characters or path components like .., /, or \. This oversight allows attackers to craft malicious inputs that escape the intended directory boundaries.

Attack Vector

The attack vector for CVE-2026-7384 is network-based, enabling remote exploitation. An attacker can send crafted requests to the search_papers function with a malicious topic parameter containing path traversal sequences.

For example, an attacker might submit a topic value such as ../../../../etc/passwd to attempt reading the system password file on Unix-based systems, or ..\..\..\..\windows\system32\config\sam on Windows systems.

The vulnerability does not require authentication or user interaction, making it particularly dangerous in exposed deployments. The project maintainer was notified via an issue report on GitHub, but has not yet responded.

Detection Methods for CVE-2026-7384

Indicators of Compromise

HTTP requests to the research_server.py endpoint containing ../ or ..\ sequences in the topic parameter
Unusual file access patterns in application logs, particularly attempts to access files outside the expected research papers directory
Log entries showing access attempts to sensitive system files such as /etc/passwd, /etc/shadow, or configuration files

Detection Strategies

Implement web application firewall (WAF) rules to detect and block path traversal patterns in request parameters
Monitor application logs for requests containing sequences like ../, ..%2f, %2e%2e/, or URL-encoded path traversal variants
Deploy runtime application self-protection (RASP) solutions to detect path traversal attempts at the application layer

Monitoring Recommendations

Enable verbose logging for the search_papers function to capture all incoming topic parameter values
Set up alerts for file access attempts outside the designated papers directory
Monitor for increased error rates that might indicate exploitation attempts

How to Mitigate CVE-2026-7384

Immediate Actions Required

Restrict network access to the affected research_server.py endpoint until a patch is available
Implement input validation at the network perimeter using a WAF or reverse proxy to filter path traversal sequences
Review application logs for any evidence of prior exploitation attempts
Consider taking the service offline if exposure cannot be adequately controlled

Patch Information

As of the last NVD update on 2026-04-29, no official patch has been released by the project maintainer. The project follows a rolling release model without versioned releases. Users should monitor the official GitHub repository for updates. The vulnerability was reported through a GitHub issue, but the project has not yet responded.

Additional technical details are available through VulDB.

Workarounds

Implement a whitelist of allowed characters for the topic parameter, rejecting any input containing path separators or traversal sequences
Use a reverse proxy or WAF to strip or block requests containing path traversal patterns before they reach the application
Run the application in a containerized or chroot environment to limit the scope of accessible files even if traversal succeeds

bash

# Example nginx configuration to block path traversal attempts
location /search_papers {
    # Block requests with path traversal patterns
    if ($request_uri ~* "\.\./|\.\.\\") {
        return 403;
    }
    
    # Block URL-encoded path traversal
    if ($request_uri ~* "%2e%2e|%252e") {
        return 403;
    }
    
    proxy_pass http://backend;
}