Categories
CVE-2026-73845 medium CVSS 5.3

Vulnerability in @aborruso/ckan-mcp-server (CVE-2026-73845)

Summary

Vulnerability in @aborruso/ckan-mcp-server (CVE-2026-73845). Risk of unauthorized operations or information disclosure. Exploitable via ckan_get_mqa_quality. 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, the ckan_get_mqa_quality and ckan_get_mqa_quality_details tools in src/tools/quality.ts use isValidMqaServer to validate the server_url parameter with a prefix-only regular expression for dati.gov.it, allowing suffix-host and URL-userinfo values to target an attacker-controlled host and return a spoofed response. This issue is fixed in version 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-73845 has been found in @aborruso/ckan-mcp-server.
Attackers can target a specific entry point like ckan_get_mqa_quality over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/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-73845" on the vendor's site.

CVE-2026-73845 (@aborruso/ckan-mcp-server) — CWE-20 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ckan_get_mqa_quality / ckan_get_mqa_quality_details / server_url / dati.gov.it
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.

❓ What is the problem

A vulnerability (CWE-20) exists in @aborruso/ckan-mcp-server. Attackers reach the vulnerable code path via ckan_get_mqa_quality without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @aborruso/ckan-mcp-server. Attack surface: ckan_get_mqa_quality / ckan_get_mqa_quality_details / server_url / dati.gov.it.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.4.112.

🛡️ 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 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

  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
    Apply patch patch
    Upgrade @aborruso/ckan-mcp-server to 0.4.112

    ステージング環境で 0.4.112 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

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

Affected packages

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

References

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