AAK-MCP-MARK3LABS-FS-CVE-2026-79534-001: mark3labs mcp-filesystem-server image (every tag): writes follow a dangling symlink out of the allowed directories
- Severity
- MEDIUM
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/container_image_pins.py- Auto-fixable
- No.
- SARIF name
Mark3labsFilesystemMcpDanglingSymlinkWrite
What it detects
mark3labs mcp-filesystem-server is a Go MCP server that ships as the image ghcr.io/mark3labs/mcp-filesystem-server and a go install binary. Its validatePath resolves symlinks with filepath.EvalSymlinks, and when that fails because the target does not exist it checks only the parent directory and returns the unresolved path. A dangling symlink placed inside an allowed directory therefore passes, and write_file, modify_file, copy_file, move_file and create_directory follow it to create a file anywhere the server's user can write (CVE-2026-79534, CVSS 3.1 5.9, CWE-22/CWE-59). The same fallback is in every release from 0.6.0 to 0.11.1, the newest, and on main; there is no fixed release, and latest is 0.11.1.
How to fix
There is no fixed release. Mount only the directories the agent needs, read-only where it only reads, and keep anything that could plant a symlink (an untrusted repository, a shared upload directory) out of the allowed directories. Pin the first fixed tag once it ships.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-MARK3LABS-FS-CVE-2026-79534-001
Limitations
Reads image references only: an image: value or any other mention of REPO:TAG in YAML (compose files, Kubernetes manifests, MCP configs), a Helm values mapping of repository (or registry + repository) and tag, Dockerfile and Containerfile FROM, and docker run arguments in *mcp*.json and claude_desktop_config.json. A tag that is not a version (main, main-20250617, dev), a digest with no tag, an interpolated tag (:${VERSION}, {{ .Values.tag }}) and a Helm tag left empty (the chart's appVersion decides) state no version and are not reported. A two-part tag such as 0.24 stands for the newest patch on that line and is reported only when the whole line sits below the fixed version. Mirrors under another registry are not matched, and commented-out lines are skipped. Every tag up to 0.11.1 is reported, and latest or no tag too, since latest was 0.11.1 on 2026-10-03. A binary from go install github.com/mark3labs/mcp-filesystem-server states no version anywhere AAK reads and is not reported.
References
- CVE: CVE-2026-79534
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP05:2025 (Command Injection & Execution)
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-INJECT-02 (Path Manipulation)
- CSA AI Controls Matrix (AICM): AIS-07, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-MARK3LABS-FS-CVE-2026-79534-001.md: the page then shows that text, with the registry reference appended under it.