GHSA-78x9-fhhx-v2g6: CKAN MCP Server: Cache-key canonicalization collision enables cache confusion / poisoning
Summary
The CKAN MCP Server has a cache-key collision vulnerability where different parameter sets can produce the same cache key, allowing an attacker to poison the cache (store malicious data in it) so that other users receive wrong results. The problem occurs because the cache key creation doesn't properly escape special characters like '&' and '=', so two genuinely different queries can be treated as identical and share the same cached response.
Solution / Mitigation
The source recommends: '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.' Additionally, 'Consider partitioning the cache per client/tenant on shared deployments so one client cannot influence another's entries.'
Vulnerability Details
EPSS: 0.1%
Yes
September 3, 2026
Classification
Taxonomy References
Affected Vendors
Affected Packages
Related Issues
CVE-2026-34371: LibreChat is a ChatGPT clone with additional features. Prior to 0.8.4, LibreChat trusts the name field returned by the e
CVE-2024-27444: langchain_experimental (aka LangChain Experimental) in LangChain before 0.1.8 allows an attacker to bypass the CVE-2023-
Original source: https://github.com/advisories/GHSA-78x9-fhhx-v2g6
First tracked: September 3, 2026 at 02:01 PM
Classified by LLM (prompt v3) · confidence: 78%