Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61612 medium CVSS 5.7

SSRF (Server-Side Request Forgery) in @aborruso/ckan-mcp-server (CVE-2026-61612)

Summary

SSRF in @aborruso/ckan-mcp-server (CVE-2026-61612). Confidential information can be exposed externally. Exploitable via POST /mcp. Mitigation: upgrade to 0.4.108 or later.

Original description

The description as published by the source.

Summary

The SSRF guard validateServerUrl (added for CVE-2026-33060, extended for CVE-2026-53509) validates only the hostname string and never resolves DNS. Any caller-supplied server_url whose hostname resolves to an internal address passes the guard, so the server issues requests to loopback and cloud metadata (169.254.169.254). This is a third bypass of the same guard, still present in the current latest 0.4.107, and it reaches IMDS — strictly more than CVE-2026-53509, which only reached loopback.

Affected / patched

  • @aborruso/ckan-mcp-server (npm) — all versions with the guard, through 0.4.107 (current latest). The guard has never resolved DNS. No patch yet.

Severity

It is effectively High for the self-hosted unauthenticated HTTP transport (TRANSPORT=http, POST /mcp), where any remote client reaches IMDS/internal hosts directly. The official Cloudflare Worker endpoint is CF-sandboxed (cannot reach loopback/RFC-1918/IMDS).

Root cause — src/utils/http.ts, validateServerUrl

The guard blocks IP literals and three loopback alias strings, but does no name resolution:

const hostname = parsed.hostname.toLowerCase();
if (new Set(['localhost','ip6-localhost','ip6-loopback']).has(hostname)) throw;   // string denylist
if (hostname.match(/^(\d+)\.(\d+)\.(\d+)\.(\d+)$/)) { /* block private/special IPv4 LITERALS */ }
// no DNS resolution → a hostname that RESOLVES to 127.0.0.1 / 169.254.169.254 / 10.x is allowed

B…

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-61612 has been found in @aborruso/ckan-mcp-server.
Attackers can target a specific entry point like POST /mcp 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.108 or later.
If unsure, ask your IT team or search "@aborruso/ckan-mcp-server CVE-2026-61612" on the vendor's site.

CVE-2026-61612 (@aborruso/ckan-mcp-server) — CWE-918 / CVSS v3 5.7
Attack vector: remote (network-reachable)
Attack surface: POST /mcp / validateServerUrl / server_url / latest
Patched: 0.4.108 — 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.

❓ What is the problem

SSRF (CWE-918) exists in @aborruso/ckan-mcp-server. Attackers reach the vulnerable code path via POST /mcp.

📍 Affected scope

Check the vendor advisory for the affected versions of @aborruso/ckan-mcp-server. Attack surface: POST /mcp / validateServerUrl / server_url / latest.

🔥 Severity

Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.4.108.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /mcp requests with malformed payloads or SQL meta-characters. 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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /mcp' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /mcp への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade @aborruso/ckan-mcp-server to 0.4.108

    ステージング環境で 0.4.108 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /mcp on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @aborruso/ckan-mcp-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.108"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details