# CVE-2026-15749: mastergo-design mastergo-magic-mcp mcp__C2d get-c2d.ts execute path traversal

> A path traversal vulnerability in mastergo-magic-mcp allows local attackers to read or modify arbitrary files via the filePath argument.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-r83c-hc4j-pvc5

## What is CVE-2026-15749?

CVE-2026-15749 is a medium-severity path traversal vulnerability in mastergo-design mastergo-magic-mcp, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw has been discovered in mastergo-design mastergo-magic-mcp up to 0.2.0. This issue affects the function execute of the file src/tools/get-c2d.ts of the component mcp__C2d. Performing a manipulation of the argument filePath results in path traversal. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. 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-15749?


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

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

## Is CVE-2026-15749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15749 is a medium-severity path traversal vulnerability in mastergo-design mastergo-magic-mcp, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15749 exists.

Affected product: mastergo-design mastergo-magic-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-15749/ (Markdown: https://insights.sbomify.com/CVE-2026-15749/index.md)
```

## Sources

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

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