CVE-2026-7149
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in the prepare_kaggle_dataset function of src/kaggle_mcp/server.py allows remote attackers to manipulate the competition_id argument to access arbitrary files on the system using directory traversal sequences (e.g., ../../).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the kaggle_mcp package installationRun 'pip show kaggle-mcp' or search for src/kaggle_mcp/server.py in your environmentAffected if The package is installed and server.py exists on the system
-
Examine the prepare_kaggle_dataset functionOpen src/kaggle_mcp/server.py and locate the prepare_kaggle_dataset function. Check if it uses the competition_id parameter in file operations without sanitizationAffected if The function directly uses competition_id in file path operations (e.g., open(), os.path.join(), Path()) without validating or sanitizing the input
-
Determine if the function is exposed via an API or server endpointCheck if the prepare_kaggle_dataset function is registered as an MCP tool, FastAPI route, or other network-accessible endpointAffected if The function is exposed as a callable API endpoint or MCP tool that accepts external input
-
Test for path traversal vulnerabilityInvoke the function with a competition_id containing directory traversal sequences (e.g., '../../etc/passwd' or '../../../../../../etc/passwd') and observe if file contents are returnedAffected if The function returns contents of files outside the intended Kaggle dataset directory
-
Check current input validation mechanismsSearch the codebase for any input validation, sanitization, or allowlist logic applied to competition_id before file operationsAffected if No validation exists or the validation can be bypassed with encoded/alternative traversal sequences
A user is affected if the kaggle_mcp package is installed, the prepare_kaggle_dataset function is exposed to external input, and the competition_id parameter is not properly validated, allowing directory traversal to read arbitrary files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on the competition_id parameter to reject path traversal sequences and enforce that file access is restricted to intended directories only.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7149 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data