SSRF (Server-Side Request Forgery) in @aborruso/ckan-mcp-server (CVE-2026-53509)
Summary
SSRF in @aborruso/ckan-mcp-server (CVE-2026-53509). Confidential information can be exposed externally. Exploitable via localhost. Mitigation: upgrade to 0.4.106 or later.
Original description
The description as published by the source.
Summary
A known vulnerability CVE-2026-33060 indicated tools including ckan_package_search and sparql_query that accept a base_url parameter had the risk of making HTTP requests to arbitrary endpoints without restriction. A fix was applied to filter out ip addresses. However, a method to bypass exists.
Details
CKAN MCP Server validates caller-supplied CKAN server URLs by inspecting only the parsed hostname string before issuing outbound HTTP requests. In src/utils/http.ts, hostname aliases such as ip6-localhost are not equal to localhost, are not dotted IPv4 literals, and are not bracketed IPv6 literals, so they pass the SSRF filter but can resolve to loopback when the server performs the request. A remote MCP caller that can invoke CKAN tools with a server_url can therefore make the server connect to local or private addresses and, for CKAN-shaped responses, receive response-derived data.
Fix
Replaced the single hostname === 'localhost' check with a blocked-hostname Set covering ip6-localhost and ip6-loopback. Patched in commit c761045a1b7c5f40d2626540dd2ef1d4feb91f8c.
@aborruso/ckan-mcp-server thanks hibrian827 for responsibly disclosing this issue.
Source: GitHub Security Advisories (Global) 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-53509 has been found in @aborruso/ckan-mcp-server.
Attackers can target a specific entry point like localhost over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.7/10.
What to do: upgrade @aborruso/ckan-mcp-server to 0.4.106 or later.
If unsure, ask your IT team or search "@aborruso/ckan-mcp-server CVE-2026-53509" on the vendor's site.
CVE-2026-53509 (@aborruso/ckan-mcp-server) — CWE-918 / CVSS v3 5.7
Attack vector: remote (network-reachable)
Attack surface: localhost / server_url / Set / c761045a1b7c5f40d2626540dd2ef1d4feb91f8c
Patched: 0.4.106 — 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.
SSRF (CWE-918) exists in @aborruso/ckan-mcp-server. Attackers reach the vulnerable code path via localhost.
Check the vendor advisory for the affected versions of @aborruso/ckan-mcp-server. Attack surface: localhost / server_url / Set / c761045a1b7c5f40d2626540dd2ef1d4feb91f8c.
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.
Update to 0.4.106.
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.106ステージング環境で 0.4.106 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。