Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.194% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.traceforce.ai/security-advisories/cve-2026-79534 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Directory Traversal via Dangling Symlink in mark3labs mcp-filesystem-server |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-59 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Directory Traversal via Dangling Symlink in mark3labs mcp-filesystem-server | |
| Weaknesses | CWE-22 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | mark3labs mcp-filesystem-server v0.11.1 is vulnerable to Directory Traversal due to an improper link resolution in validatePath (filesystemserver/handler/helper.go). When filepath.EvalSymlinks returns os.IsNotExist for a dangling symlink, the fallback validates only the parent directory and returns the unresolved path, so write_file (and modify_file, copy_file, move_file, create_directory) follows a pre-existing dangling symlink located inside an allowed directory and creates a file outside the configured allowed directories. | |
| References |
|
No data.