Vulnerability in @aborruso/ckan-mcp-server (CVE-2026-73844)
Summary
Vulnerability in @aborruso/ckan-mcp-server (CVE-2026-73844). Risk of unauthorized operations or information disclosure. Exploitable via formatCkanError. Mitigation: upgrade to 0.4.112 or later.
Original description
The description as published by the source.
CKAN MCP Server is a tool for querying CKAN open data portals. Prior to 0.4.112, 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). This vulnerability is fixed in 0.4.112.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73844 has been found in @aborruso/ckan-mcp-server.
Attackers can target a specific entry point like formatCkanError over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade @aborruso/ckan-mcp-server to 0.4.112 or later.
If unsure, ask your IT team or search "@aborruso/ckan-mcp-server CVE-2026-73844" on the vendor's site.
CVE-2026-73844 (@aborruso/ckan-mcp-server) — CWE-209 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: formatCkanError / Error.message / data / error.message
Patched: 0.4.112 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-209) exists in @aborruso/ckan-mcp-server. Attackers reach the vulnerable code path via formatCkanError without authentication.
Check the vendor advisory for the affected versions of @aborruso/ckan-mcp-server. Attack surface: formatCkanError / Error.message / data / error.message.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 0.4.112.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@aborruso/ckan-mcp-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@aborruso/ckan-mcp-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@aborruso/ckan-mcp-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @aborruso/ckan-mcp-server to 0.4.112ステージング環境で 0.4.112 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com