CKAN MCP Server: Information disclosure via verbose error reflection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-73844: 0.36% estimated exploitation activity in the next 30 days; percentile 29.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Error paths reflect raw upstream response bodies and internal exception messages back to the caller instead of a sanitized, generic message. When the server is pointed at (or redirected/SSRF'd to) a host that returns a non-CKAN response, or when an internal exception occurs, the caller receives verbatim upstream content and internal detail (hostnames, internal IPs, DB errors, stack fragments). Affected code src/utils/http.ts — the entire decoded upstream body is embedded in the thrown error, which formatCkanError returns to the tool result: src/worker.ts — the catch-all handler returns the raw Error.message in the JSON-RPC data field: Impact - Reflects arbitrary upstream response content to the caller. Combined with the SSRF vectors (advisories #01/#06), an attacker can use this as the read channel: point the server at an internal endpoint and receive its body inside the success=false error string (turning otherwise-blind SSRF into a semi-blind/return-value SSRF for any host…

Published by the source

3 Sep 2026, 14:49 UTC

Last modified by the source

3 Sep 2026, 14:49 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6f9w-9hf2-5rg3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73844

Advisory: CKAN MCP Server: Information disclosure via verbose error reflection
IDs: CVE-2026-73844, GHSA-6f9w-9hf2-5rg3
Record: https://patchnext.com/advisories/cve-2026-73844 (revision 1, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @aborruso/ckan-mcp-server 0.4.112. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @aborruso/ckan-mcp-server: affected < 0.4.112; fixed in 0.4.112

## Suggested inspection (read-only)
- `npm ls @aborruso/ckan-mcp-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @aborruso/ckan-mcp-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6f9w-9hf2-5rg3 (GitHub-reviewed advisory GHSA-6f9w-9hf2-5rg3 lists affected ranges: npm @aborruso/ckan-mcp-server >=0 <0.4.112)

Commands are suggestions: review each one before running it.