AAK-MCP-KNOWNS-CVE-2026-86439-001: knowns MCP doc/memory and code.find tools: path traversal outside the project directory (no fixed release)
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
KnownsMcpPathTraversal
What it detects
knowns (knowns, npm — knowns-dev) before 0.30.0 does not validate filesystem paths supplied in MCP tool arguments, so an attacker-controlled path containing directory-traversal sequences reads, creates, overwrites or deletes files outside the project directory (CVE-2026-86439, CVSS 8.8). NVD scopes the read reach to "arbitrary Markdown files accessible to the server process", which follows from where the defect sits: the document and memory stores (internal/storage/doc_store.go, internal/storage/memory_store.go) are Markdown-backed. Fixed in v0.30.0. CVE-2026-88938 (MEDIUM 6.5) then reopened the same class on a different tool: knowns through 0.33.0 does not confine the path argument of the code.find MCP tool to the project root, so an agent session supplies an absolute path or traversal sequence and retrieves full file contents from anywhere the server process can read. Its advisory (GHSA-5cj9-fcqq-g2h7) names no patched version, and the releases published since 0.33.0 are not confirmed fixed, so there is no fix floor to upgrade to and this pin is presence-only: it fires on any referenced version. That holds until upstream names a fixed release, and is not a placeholder — the same shape as the postgres-mcp and mcp-florence2 pins in this table.
How to fix
No release is confirmed fixed. Until upstream names one, run knowns against a directory that contains nothing the agent session should not read, or drop it. When a fixed release is named, upgrade to it and pin it. The upstream fix has to resolve every path taken from a tool argument and reject any result that escapes the project root before opening it.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-KNOWNS-CVE-2026-86439-001
Limitations
Reads knowns in requirements*.txt at any depth and, at the project root only, in pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock, uv.lock, package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles, and reports every version from 0.1.1 on, a future fixed one included, until the pin gets a floor. The dependency is not read when it is declared in a sub-directory manifest (packages/app/package.json), in .cursor/mcp.json or .vscode/mcp.json, or in a lockfile format the reader does not parse (a Yarn 2+ yarn.lock). The npm release 0.1.0 is affected too but is not reported, because the same number belongs to an unrelated PyPI package of that name. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-86439, CVE-2026-88938
- 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-DATA-01
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-KNOWNS-CVE-2026-86439-001.md: the page then shows that text, with the registry reference appended under it.