CVE-2026-15749
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 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.
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 · moderate confidenceA path traversal vulnerability exists in the mastergo-magic-mcp component mcp__C2d, specifically in the execute function within src/tools/get-c2d.ts. The filePath argument is not properly validated, allowing an attacker to use traversal sequences (e.g., ../../../') to access files outside the intended directory. This is a local attack vector requiring code execution capability.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/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 mastergo-magic-mcp package installationRun 'npm list mastergo-magic-mcp' or check package.json dependencies in your projectAffected if The package is installed and you have no patched version
-
Identify installed versionRun 'npm list mastergo-magic-mcp' to see the exact version number, or check node_modules/mastergo-magic-mcp/package.jsonAffected if Version is unpatched and falls within any vulnerable range (compare to any known fixed version)
-
Verify vulnerable code existsInspect node_modules/mastergo-magic-mcp/src/tools/get-c2d.ts and check if the execute function handles a filePath argument without validationAffected if The filePath argument in get-c2d.ts execute function lacks proper path traversal validation (no whitelist, no canonical path resolution, no traversal sequence rejection)
-
Check if mcp__C2d component is exposedReview your MCP server configuration or startup code to determine if the mcp__C2d tool is registered and accessibleAffected if The mcp__C2d tool is enabled and accessible to callers who can supply the filePath argument
-
Verify input handling for filePathReview any middleware, wrapper code, or configuration around the get-c2d.ts execute call to see if filePath validation occurs before passing to the execute functionAffected if No input validation or sanitization is performed on the filePath argument before it reaches the vulnerable execute function
You are affected if mastergo-magic-mcp is installed, contains unvalidated filePath handling in the mcp__C2d/get-c2d.ts component, and that component is accessible to supply malicious traversal sequences.
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 filePath argument to restrict access to an allowed directory whitelist, normalize the path using canonical path resolution, and reject any path containing traversal sequences or absolute paths outside the permitted scope.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15749 — 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-15749 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