# CVE-2026-7149: dexhunter kaggle-mcp server.py prepare_kaggle_dataset path traversal

> Remote attackers can exploit path traversal in the Kaggle MCP server to read or modify arbitrary files via the competition_id argument.

- **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:** 27 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-q882-jc55-6343, PYSEC-2026-2542

## What is CVE-2026-7149?

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

### Official description

A vulnerability has been found in dexhunter kaggle-mcp up to 406127ffcb2b91b8c10e20e6c2ca787fbc1dc92d. This vulnerability affects the function prepare_kaggle_dataset of the file src/kaggle_mcp/server.py. The manipulation of the argument competition_id leads to path traversal. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. 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-7149?

3 open source packages ship an affected version, including kaggle-mcp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kaggle-mcp` | PyPI | All versions to 0.1.0 | None |
| `kaggle-mcp` | PyPI | All versions to 0.1.0 | None |
| `kaggle-mcp` | PyPI | All versions to 0.1.0 | None |

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

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

## Is CVE-2026-7149 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7149 is a medium-severity path traversal vulnerability in dexhunter kaggle-mcp, published on 27 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-7149 exists.

Affected packages and fixed versions:
- kaggle-mcp (PyPI): affected all versions up to 0.1.0; no fix listed
- kaggle-mcp (PyPI): affected all versions up to 0.1.0; no fix listed
- kaggle-mcp (PyPI): affected all versions up to 0.1.0; no fix listed

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-7149/ (Markdown: https://insights.sbomify.com/CVE-2026-7149/index.md)
```

## Sources

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

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