# CVE-2026-7384: ezequiroga mcp-bases research_server.py search_papers path traversal

> Attackers can exploit path traversal in the search_papers function to read arbitrary files from the server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 29 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-v8h5-8596-45g9

## What is CVE-2026-7384?

CVE-2026-7384 is a medium-severity path traversal vulnerability in ezequiroga mcp-bases, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in ezequiroga mcp-bases 357ca19c7a49a9b9cb2ef639b366f03aba8bea39/c630b8ab0f970614d42da8e566e9c0d15a16414c. This impacts the function search_papers of the file research_server.py. Performing a manipulation of the argument topic results in path traversal. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. 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-7384?


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

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

## Is CVE-2026-7384 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7384 is a medium-severity path traversal vulnerability in ezequiroga mcp-bases, published on 29 Apr 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-7384 exists.

Affected product: ezequiroga mcp-bases. 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-7384/ (Markdown: https://insights.sbomify.com/CVE-2026-7384/index.md)
```

## Sources

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

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