UTC
Medium

CKAN MCP Server: Cache-key canonicalization collision enables cache confusion / poisoning

CVE-2026-73846 · GHSA-78x9-fhhx-v2g6 · published 2026-09-03

Severity
Medium
CVSS score
6.5
Chance of exploitation (EPSS)
0.19%
Fixed in
0.4.112
  • Exploitation Public proof of concept
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

Cache poisoning / confusion. On a shared cache (caching is enabled by default; the Cloudflare Workers deployment uses the shared caches.default, and a Node HTTP instance shares one in-process LRU across all clients), an attacker primes a colliding entry so that another client's genuinely different query receives the attacker-chosen response for the same portal. Integrity of results. Victims receive data for a query they did not make (wrong dataset list, wrong record set), undermining trust in tool output. Chains with indirect prompt injection (advisory #07).

What to do

Upgrade @aborruso/ckan-mcp-server to 0.4.112 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Build the cache key from an unambiguous, injection-proof encoding: hash a structured, canonical JSON (with typed values) or percent-encode/escape each key and value before joining, and use a separator that cannot appear in the encoded fields. Include a type tag so {a:{...}} (object) and {a:"..."} (string) never coincide. Consider partitioning the cache per client/tenant on shared deployments so one client cannot influence another's entries.

Affected
PackageRegistryAffectedFixed in
@aborruso/ckan-mcp-servernpm< 0.4.1120.4.112

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].