Skip to content

AAK-MCP-ARGOCD-CVE-2026-108585-001: argocd-mcp builds Argo CD API paths from tool arguments, so delete_application can reach repositories and clusters (no fixed release)

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
ArgoCdMcpDeleteApplicationPathTraversal

What it detects

argocd-mcp (npm; argoproj-labs/mcp-for-argocd), the Argo CD MCP server, puts the applicationName tool argument into Argo CD API paths unencoded, and its HTTP client resolves each path against the base URL with new URL, which collapses dot segments. So a delete_application call whose name is ../repositories/<repo> sends an authenticated DELETE to /api/v1/repositories/<repo>, and the same reaches clusters and projects, within the API token's RBAC. An agent that reads untrusted text can be steered into that call (CVE-2026-108585, CVSS 3.1 5.4, CWE-22). Every published version builds the path this way (0.0.1, the first, through 0.9.0, the newest), there is no commit after 0.9.0, and there is no fixed release, so this is a presence-only pin.

How to fix

There is no fixed release. Set MCP_READ_ONLY=true, which turns off the tools that change or delete resources, or give the server an Argo CD token whose RBAC has no delete permission on repositories, clusters or projects. Pin the first fixed release once it ships.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-ARGOCD-CVE-2026-108585-001

Limitations

Reports a reference that names argocd-mcp: a package.json or lockfile entry, or the package in an MCP config, such as the README's npx argocd-mcp@latest stdio. Presence-only: every version is reported, a future fixed one included, until the pin gets a floor, and MCP_READ_ONLY is not read. argocd-mcp-server and mcp-argocd are other projects and are not matched. The project's images (ghcr.io/argoproj-labs/mcp-for-argocd, quay.io/argoprojlabs/mcp-for-argocd) are not read. 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


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-ARGOCD-CVE-2026-108585-001.md: the page then shows that text, with the registry reference appended under it.