dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7272

HIGH · 7.3 CVSS v3.1 Published 2026-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A flaw has been found in WilliamCloudQi matlab-mcp-server up to ab88f6b9bf5f36f725e8628029f7f6dd0d9913ca. The affected element is the function generate_matlab_code/execute_matlab_code of the file src/index.ts of the component MCP Interface. Executing a manipulation of the argument scriptPath can lead to path traversal. The attack can be executed remotely. The exploit has been published 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 confidence

A path traversal vulnerability exists in WilliamCloudQi's matlab-mcp-server MCP Interface (src/index.ts), specifically in the generate_matlab_code and execute_matlab_code functions. The scriptPath parameter is not properly validated, allowing remote attackers to manipulate it using directory traversal sequences (e.g., ../../) to access files outside the intended directory.

MitigationImplement strict input validation on the scriptPath parameter using allowlist patterns, perform path canonicalization (realpath) to resolve symlinks and normalize paths, and verify the final resolved path stays within an authorized base directory before any file operations.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if matlab-mcp-server is installed
    Check your node_modules or Python environment for the @williamcloudqi/matlab-mcp-server package, or look for the src/index.ts file in your project. Run 'npm list @williamcloudqi/matlab-mcp-server' or 'pip list | grep matlab-mcp-server' depending on your package manager.
    Affected if The package is not present in your environment
  2. Determine the installed version
    Run 'npm list @williamcloudqi/matlab-mcp-server version' or check the package.json version field. Compare your version against any available patched versions from the vendor.
    Affected if You have an older unpatched version of matlab-mcp-server installed
  3. Verify the MCP server exposes the vulnerable functions
    Inspect the src/index.ts file in the matlab-mcp-server installation directory. Look for the generate_matlab_code and execute_matlab_code function definitions and confirm they accept a scriptPath parameter.
    Affected if Your installation contains src/index.ts with these functions accepting scriptPath parameter
  4. Check if input validation exists on scriptPath
    Review the source code for the generate_matlab_code and execute_matlab_code functions. Look for path validation logic such as allowlist patterns, realpath canonicalization, or base directory enforcement before file operations.
    Affected if No path validation, allowlisting, or directory containment checks are found in the code handling scriptPath
  5. Test if directory traversal is possible
    If you have access to the MCP interface, attempt to invoke the function with a scriptPath containing traversal sequences like ../../etc/passwd or ../../../../../../../../etc/hostname and observe if files outside the intended directory are accessed or returned.
    Affected if The function returns file contents from paths outside the intended base directory when using ../ sequences

You are affected if you have the WilliamCloudQi matlab-mcp-server installed with vulnerable generate_matlab_code or execute_matlab_code functions accessible and no input validation exists on the scriptPath parameter to prevent directory traversal.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the scriptPath parameter using allowlist patterns, perform path canonicalization (realpath) to resolve symlinks and normalize paths, and verify the final resolved path stays within an authorized base directory before any file operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7272 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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