# CVE-2026-7627: 8nite metatrader-4-mcp sync_ea_from_file index.ts CallToolRequestSchema path traversal

> Remote attackers can exploit path traversal in the sync_ea_from_file function to read or modify arbitrary files via the ea_name argument.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-g88g-gjr5-6xh7

## What is CVE-2026-7627?

CVE-2026-7627 is a medium-severity path traversal vulnerability in 8nite metatrader-4-mcp, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in 8nite metatrader-4-mcp 1.0.0. This vulnerability affects the function CallToolRequestSchema of the file src/index.ts of the component sync_ea_from_file. Such manipulation of the argument ea_name leads to path traversal. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. 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-7627?


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

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

## Is CVE-2026-7627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7627 is a medium-severity path traversal vulnerability in 8nite metatrader-4-mcp, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7627 exists.

Affected product: 8nite metatrader-4-mcp. 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-7627/ (Markdown: https://insights.sbomify.com/CVE-2026-7627/index.md)
```

## Sources

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

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