CVE-2026-7594
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 was detected in Flux159 mcp-game-asset-gen 0.1.0. Affected is the function image_to_3d_async of the file src/index.ts of the component MCP Interface. The manipulation of the argument statusFile results in path traversal. The attack can be executed remotely. The exploit is now public and may be used. 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 confidencePath traversal vulnerability in the image_to_3d_async function within src/index.ts of the MCP Interface. The statusFile argument lacks proper input validation, allowing attackers to manipulate file paths using sequences like ../ to access or write files outside the intended directory. This is exploitable remotely and a public exploit exists.
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.
-
Identify installed MCP Interface versionRun 'npm list mcp-interface' or check package.json for the @modelcontextprotocol/server or similar MCP Interface package versionAffected if Version is within the affected range and has not been patched for CVE-2026-7594
-
Locate the image_to_3d_async function in source codeSearch for 'image_to_3d_async' in src/index.ts or the installed package source code and examine the function definitionAffected if The function exists and accepts a statusFile parameter without proper validation
-
Inspect statusFile parameter validationReview the code handling the statusFile argument in the image_to_3d_async function for input sanitization or path validation logicAffected if No validation exists that blocks ../ path traversal sequences in the statusFile parameter
-
Check if the function is exposed via API or CLIReview the exposed endpoints, command handlers, or API routes that call image_to_3d_async to determine if external input can reach the vulnerable parameterAffected if The function is reachable via remote API calls or exposed interfaces without authentication barriers
-
Verify file operation scopeCheck the file system operations performed using the statusFile path - look for readFile, writeFile, or similar operations that use the unsanitized pathAffected if File operations use the statusFile parameter directly without path resolution or directory containment checks
Your environment is affected if you run a vulnerable version of the MCP Interface with the image_to_3d_async function exposed and the statusFile parameter lacks validation against path 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 statusFile parameter to reject path traversal sequences and restrict file operations to a safe, whitelisted directory. Use canonical path resolution and verify the resolved path stays within allowed boundaries.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7594 — 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-7594 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