# CVE-2026-7386: fatbobman mail-mcp-bridge mail_mcp_server.py path traversal

> Remote attackers can exploit path traversal in mail-mcp-bridge to access unauthorized files via manipulated message IDs.

- **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-2gfj-fr43-4735

## What is CVE-2026-7386?

CVE-2026-7386 is a medium-severity path traversal vulnerability in fatbobman mail-mcp-bridge, 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 flaw has been found in fatbobman mail-mcp-bridge up to 1.3.3. Affected is an unknown function of the file src/mail_mcp_server.py. Executing a manipulation of the argument message_ids can lead to path traversal. The attack can be executed remotely. The exploit has been published and may be used. Upgrading to version 1.3.4 is able to address this issue. This patch is called 638b162b26532e32fa8d8047f638537dbdfe197a. Upgrading the affected component is recommended.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-7386?


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

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

## Is CVE-2026-7386 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7386 is a medium-severity path traversal vulnerability in fatbobman mail-mcp-bridge, 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-7386 exists.

Affected product: fatbobman mail-mcp-bridge. 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-7386/ (Markdown: https://insights.sbomify.com/CVE-2026-7386/index.md)
```

## Sources

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

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