CVE-2026-73844: CKAN MCP Server information disclosure via error reflection

CVE-2026-73844 · Severity: low · CVSS 3.7 · Published 2026-08-14

The CKAN MCP Server is a middleware tool that interfaces with CKAN data repositories. When errors occur—either from upstream services or internal failures—the server returns raw error details and response content to callers, including internal IP addresses, database error messages, and server hostnames. An attacker can exploit this to discover internal infrastructure details and, when combined with Server-Side Request Forgery (SSRF) vulnerabilities, read sensitive content from internal endpoints.

Technologies: @aborruso/ckan-mcp-server (npm), Ondata Ckan-Mcp-Server. Vendors: npm, Ondata.

Quick answers

Is CVE-2026-73844 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-73844 being exploited in the wild.
How severe is CVE-2026-73844?
Low severity, with a CVSS score of 3.7, published 14 August 2026.
Which products and versions are affected?
@aborruso/ckan-mcp-server (npm) < 0.4.112, SEMVER:introduced=0,fixed=0.4.112; Ondata Ckan-Mcp-Server < 0.4.112.
Is there a fix for CVE-2026-73844?
Yes. @aborruso/ckan-mcp-server (npm): upgrade to 0.4.112 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73844 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-73844?
Check whether you run @aborruso/ckan-mcp-server (npm) or Ondata Ckan-Mcp-Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • @aborruso/ckan-mcp-server (npm): upgrade to 0.4.112 or later
    npm install @aborruso/ckan-mcp-server@0.4.112

Technical details

The vulnerability exists in two code paths: (1) `src/utils/http.ts` embeds the full decoded upstream response body in thrown `CkanApiError` exceptions via `JSON.stringify(decodedData)`, which are returned unfiltered to callers; (2) `src/worker.ts` catch-all handler returns raw `Error.message` in the JSON-RPC `data` field at HTTP 500 status. The root cause is absence of error message sanitization—no redaction or generic error wrapping occurs before responses reach callers. An attacker can leverage this as an information disclosure oracle: by pointing the server at internal endpoints (via SSRF), they receive forbidden response bodies embedded in error messages, converting blind SSRF into data-leaking SSRF. Additionally, network errors (e.g., `ECONNREFUSED 169.254.169.254:80`) leak target addresses and confirm internal infrastructure topology. The vulnerability requires network access to the MCP Server and no authentication; the server itself holds no credentials, but amplifies SSRF attack impact. A fix is available in version 0.4.112 and later, which redacts error content server-side and returns generic messages to callers.

Affected products

  • ondata CKAN MCP Server < 0.4.112

Identifiers

  • CVE-2026-73844
  • GHSA-6f9w-9hf2-5rg3

Timeline

  • 2026-07-09: disclosed
  • 2026-09-03: advisory
  • 2026-09-03: patched: Version 0.4.112 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.