GitHub disclosed a fourth and fifth CVE record against the CKAN MCP Server: a cache-key collision and a verbose-error leak, both fixed in the same release as the third

GitHub's CNA published two more CVE records against the CKAN MCP Server on 2026-08-14, the same day it published the third record against the same server's URL validation. Together the two bring the total to five.

CVE-2026-73846, rated 6.5 medium, covers a cache-key collision. canonicalizeParams in src/utils/cache.ts serialized request parameters with unescaped ampersand, equals-sign, and vertical-bar delimiters, so distinct logical parameter sets that buildCacheKey was meant to keep apart could collide. A caller could use the collision to prime the shared cache with a response for a victim's separate query.

CVE-2026-73844, rated 3.7 low, is a verbose-error leak. Error paths reflected raw upstream response bodies and internal exception messages back to the caller instead of a sanitized message. Pointing the server at, or redirecting it to, a host that returned a non-CKAN response exposed verbatim upstream content and internal detail: hostnames, internal IP addresses, database errors, stack fragments.

Both records name ondata/ckan-mcp-server before 0.4.112 as affected, and both were fixed in that same release, published 2026-07-09, five weeks before either CVE record. The same v0.4.112 release also fixed the third record's allowlist bypass, so one version closed three separate defects that reached CVE records on the same day and then sat for weeks before appearing in GitHub's Advisory Database: the third record's listing appeared 2026-09-02, and these two followed a day later on 2026-09-03. Neither new record cites an independent researcher disclosure beyond the maintainer's own advisory text.