AAK-MCP-CKAN-CVE-2026-73846-001: @aborruso/ckan-mcp-server below 0.4.112 (cache-key collision, prefix-only host check, verbose errors)
- Severity
- MEDIUM
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
CkanMcpServerCacheAndHostValidation
What it detects
@aborruso/ckan-mcp-server, an MCP server for querying CKAN open-data portals, before 0.4.112 carries three related defects. canonicalizeParams in src/utils/cache.ts serialises request parameters without escaping &, = or |, so distinct logical parameter sets collapse to the same buildCacheKey output and an attacker can prime the shared cache with a response another user's different query then receives (CVE-2026-73846, CVSS 6.5). isValidMqaServer, used by ckan_get_mqa_quality and ckan_get_mqa_quality_details in src/tools/quality.ts, validates the server_url parameter with a prefix-only regular expression for dati.gov.it, which suffix-host and URL-userinfo forms defeat, letting a caller point the tool at an attacker-controlled host and receive a spoofed response (CVE-2026-73845, CVSS 5.3). Error paths reflect raw upstream response bodies and internal exception text — hostnames, internal IPs, database errors, stack fragments — back to the caller instead of a sanitised message (CVE-2026-73844, CVSS 3.7). All three are fixed in 0.4.112.
How to fix
Upgrade @aborruso/ckan-mcp-server to >= 0.4.112 and pin it. The three share a root cause worth fixing in any MCP server: build cache keys from a structured, escaped encoding rather than string concatenation; validate a caller-supplied host by parsing the URL and comparing the resolved host exactly, never by prefix-matching the raw string; and return a generic error to the caller while logging the detail server-side.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-CKAN-CVE-2026-73846-001
Limitations
Reads @aborruso/ckan-mcp-server 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, taking the lowest version a range allows and reporting a reference that states no version. 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). 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-73846, CVE-2026-73845, CVE-2026-73844, CVE-2026-53509, CVE-2026-61612
- 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-SSRF-01 (Internal Network MCP)
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-CKAN-CVE-2026-73846-001.md: the page then shows that text, with the registry reference appended under it.